Comments
3 comments
-
When doing a 'get latest' we don't currently show the script _unless_ the script fails to execute. Is there any reason why you need to review the script at this stage. Are you doing 'get latest' do a dev instance or production?
-
The process they were going to use was check all changes in (commit) from the QA/Dev server and then use get latest to push the changes to the production sql server. I did a little digging though and it appears you don't recommend that method. Instead we should use SQL change automation to create migration scripts. Is that correct?
-
Yes, "get latest" isn't the correct way to deploy to Production. Most customers fire up a copy of SQL Compare Pro and use this. Just set the source to the SQL Source Control scripts folder, and set the target to be your Production server and run through the deployment wizard. SCA is appropriate if you want to use a migrations-based approach for deployments, which is popular for automated release processes.
Add comment
Please sign in to leave a comment.
I feel like this should be answered somewhere, but my google foo must be low. If I need to use SQL Change automation instead, that can be the answer and I'll just need to figure out that tool.
Thanks!