Settings and activity
2 results found
-
480 votes
Thank you everyone for your comments and votes on this over the years. While I don’t have a 100% full resolution for this suggestion, I can sum up our current recommendations here. Continued feedback is very welcome.
Our current recommendation is to use the post-deployment script feature of SQL Source Control (released in V6.3) to manage SQL Server Agent jobs.
An example script for this is here: https://documentation.red-gate.com/soc/common-tasks/working-with-pre-post-deployment-scripts/create-sql-server-agent-job
As some commenters in this thread have alluded to, it is possible (and sometimes very common) for SQL Agent jobs to have steps that touch multiple databases on a single SQL Server Instance. For this reason, some customers prefer to create a separate database for instance-level management and objects (sometimes named DBA or similar) and choose to manage things like linked servers and SQL Agent jobs with the post-script associated with that database.
This separate-database architecture also makes sense if the jobs…
An error occurred while saving the comment 
Kevin Wathen
supported this idea
·
-
43 votes
SQL Compare 8.50 comes with the SSMS Integration Pack, which allows you to get the latest version of the db or a specific version of the db to a new database. This will use all the defaults for your new db.
For more information, see http://www.red-gate.com/supportcenter/Content.aspx?p=SQL%20Compare&c=SQL_Compare/help/8.50/ssmsip_deploy_new_database.htm&toc=SQL_Compare/help/8.50/toc1280663.htm.
Kevin Wathen
supported this idea
·
Ditto to all comments below