Settings and activity
8 results found
-
86 votesJ. Verdurmen supported this idea ·
-
215 votesJ. Verdurmen 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…
J. Verdurmen supported this idea · -
345 votesJ. Verdurmen supported this idea ·
-
212 votesJ. Verdurmen supported this idea ·
-
153 votesJ. Verdurmen supported this idea ·
-
103 votesJ. Verdurmen supported this idea ·
-
58 votes
We’re going to be reviewing this over the next couple of months, which would be released via the SQL Prompt for Teams EAP (get in touch if you want to know more).
In the meantime please add any other information that you think would be useful.
J. Verdurmen supported this idea ·