We are using database projects for our deployment on work and production servers, running our current process manually Has been saved for one Compare the SCMP file that compares the database project to our production database (using read only access), then produces a SQL script that we give to our IT man's support to run the production. We also create one to prepare the post deployment script, and we also give it to run with us.
I try to automate this process as much as possible (to reduce the likelihood of mistakes and make it more efficient) I want to know that the use of predefined options in our SSPM file There is a way to automatically generate a SQL Conversion Script while doing it.
In addition to this, automatically add an easy way to add post-deployment to script at the end of the schema conversion script, so there is only one SQL file to run it?
Perhaps there is a way to do the whole thing with powers or something.
OK what you should do is use sqlpackage.exe to create your script from dacpac Which is produced by the creation of the ssdt project.
Create a batch script to call it or make it a part of your CI process.
There are a few new options for filtering out the output such as the Ssdt released in the latest type (March 2015) or use a deployment filter such as:
If you need more flexibility .
Using this, you can filter the deployment as a comparison and pre / post posted script is pre / attached, then you kill two BIs with a stone RDS! Ad
No comments:
Post a Comment