Settings and activity
10 results found
-
43 votes
Philipp Häfelfinger
supported this idea
·
-
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…
Philipp Häfelfinger
supported this idea
·
-
476 votes
Thank you everyone for the suggestions and votes for this over the years.
I’d like to surface up a workaround for the “linking” problem which is mentioned in the comments. For the use case of easing pains around environment setup with a large number of databases, we have had customers find success using code based off Alessandro Alpi’s blog post: https://alessandroalpi.blog/2016/06/28/automatically-link-databases-to-red-gate-sql-source-control/
I do understand that this is a broader issue and hear that many of you also want command line or API support for the product in general.
If there are specific scenarios or workflows that would be useful to automate for you, this feedback is also very useful, and if you have details on the type of VCS you use and the workflow (such as a branching model) that it would fit in to, that would be very helpful for us to hear as well.
Philipp Häfelfinger
supported this idea
·
-
27 votes
For now, you may be able to use a batch file that executes SQL and drops the objects you want re-created before using the SQL Compare Command Line API. Since the objects are dropped, the synch script will generate CREATE scripts instead of alter.
If you wanted to create everything from scratch, you could drop and recreate the database, which would generate all CREATE scripts.
I hope this helps for now.
-
1 votePhilipp Häfelfinger
shared this idea
·
-
35 votes
For now, enter your BugID into the comment field when you commit changes.
Please continue to vote/comment here if you would like to see a seperate Bug ID box like TSVN has. See James’ comment for more details.
-
38 votes
-
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.
-
131 votes
-
156 votesPhilipp Häfelfinger
supported this idea
·
