Comments
Sort by recent activity
Step 1 of our process runs DLM Automation/SQL Compare to determine what changed in the recent TFS commit, and create a nuget package, that is sent to our Continuous Deployment app (OctopusDeploy).
When the step 'Deploy from package' (in OctopusDeploy) is executed, part of what it does is execute SQL Compare against the target server & database, to determine what changes are necessary to match the version we want to deploy.
I can see from the logs that SQL scripts are created, then executed. But when I look at that temp folder after the step is complete, the files are [naturally] automatically cleaned up. I'm looking for an option in SQL Compare that leaves the files and does not clean them up (I can add a step post to clean it). / comments
Step 1 of our process runs DLM Automation/SQL Compare to determine what changed in the recent TFS commit, and create a nuget package, that is sent to our Continuous Deployment app (OctopusDeploy).
...
No, we're using 'Deploy from package' - since VSTS already build the changes (based on what was checked in) that are needed. I'll explore this as a first step to potentially gaining access to the SQL changes that might be deployed, but it means we'll end up calling SQLCompare twice. / comments
No, we're using 'Deploy from package' - since VSTS already build the changes (based on what was checked in) that are needed. I'll explore this as a first step to potentially gaining access to the ...
Okay that's what I expected. So there's currently no step to actually create the database itself - that's something we'd have to create a custom step for and use before the RedGate deployment step?
Easy enough, just figured it had been done before. / comments
Okay that's what I expected. So there's currently no step to actually create the database itself - that's something we'd have to create a custom step for and use before the RedGate deployment step...
Excellent. Thanks guys! / comments
Excellent. Thanks guys!
The first nuget package I created was the database creation & schema script. So ideally I'd want that package (or those changes), as well as my recent change(s) to be deployed to the new server.
Imagine I have version 1.0, 1.1, and 1.2 committed in my source control, and thus 3 packages in OctopusDeploy. Now I have a SQL server I want to promote these changes to. What's the best way to setup that deploy process so it gets up to date? / comments
The first nuget package I created was the database creation & schema script. So ideally I'd want that package (or those changes), as well as my recent change(s) to be deployed to the new server.
I...
You're right, despite having reviewed the repository tabs 15 times, I some how missed the base path that was entered. Thanks! / comments
You're right, despite having reviewed the repository tabs 15 times, I some how missed the base path that was entered. Thanks!