sqlpackage vs sqlcmd

sqlpackage is a tool that allows us to deploy sqlproj/dacpac/bacpac files across different platform such as windows, linux. It uses a slightly different sqlproj format - removing some of the dependencies sqlproj has on msbuild. 

Unfortunately it cannot be used for ispac / ssis packages. 

I was abit confused when the docs mentioned SqlAzureDacpacDeployment - giving me the impression that sqlpackages is readily available as an azure devops task.  Upon some googling - this tasks uses sqlcmd. 

The differences between sqlpackage and sqlcmd are highlighted below:- 


Key Differences

FeatureSqlPackagesqlcmd
Primary PurposeDatabase schema and data management (DACPAC/BACPAC).SQL script execution and database interaction.
Typical Use Cases- Deploying database schemas.
- Extracting or exporting schemas and data.
- Publishing database updates.		- Running ad hoc T-SQL commands.
- Automating scripts for database tasks.
- Querying or modifying data directly.
Input/OutputWorks with DACPAC/BACPAC files.Works with raw T-SQL scripts or queries.
AutomationBest for CI/CD pipelines for schema deployments.Best for running routine tasks or ad hoc queries.
Cross-PlatformYes.Yes.





Comments

Post a Comment

Popular posts from this blog

The specified initialization vector (IV) does not match the block size for this algorithm

Image
If you're getting  exception when trying to assigned key to a symmetric key and getting error message below :- The specified initialization vector (IV) does not match the block size for this algorithm And your code probably look like something below :- Then you need to go into debug mode and start looking into the supported size for IV as shown in diagram below :- As you can see, IV is 16 bytes, so you need to provide 16 bytes. The same goes for Key field too, if you're adding anything to it. As long as you provide a valid key size, then we're good and you're code will be ready.
Read more