Settings and activity
18 results found
-
138 votes
An error occurred while saving the comment -
304 votes
Given the upcoming retirement of Azure Data Studio we'd be really interested to hear from our community about where you'll be moving your database development.
If you'd like to chat about your development workflow and hear about our roadmap plans drop me an email and we'll get something set up.
Thanks,
Tim
Robert
supported this idea
·
-
14 votes
Robert
supported this idea
·
-
12 votes
Robert
supported this idea
·
-
87 votes
Robert
supported this idea
·
-
22 votes
Robert
supported this idea
·
-
49 votes
Robert
supported this idea
·
-
1 vote
Robert
shared this idea
·
-
37 votes
Robert
supported this idea
·
-
104 votes
Robert
supported this idea
·
-
254 votes
Hi all. Thank you for your votes and feedback on this issue over the years. Here is our current guidance for this suggestion:
Post-deployment scripts give you flexibility for static data
With SQL Source Control, you can now use a post-deployment script to “dynamically” deploy static data based on a factor such as @@SERVERNAME or other query-able conditions.
SQL Source Control introduced pre- and post- scripts in v6.3.
An example post-deployment script which shows how to control deployment of static data by environment is here: https://documentation.red-gate.com/soc7/common-tasks/working-with-pre-post-deployment-scripts/static-data
If you make heavy use of Static Data, we have stronger support for this in SQL Change Automation.
SQL Change Automation:
- Supports column filtered static data tables in the SCA plugin in SSMS
Supports multiple post-deployment scripts, in case there is a preference to manage static data tables in dedicated post-deployment scripts - Allows approaches like bulk loading larger static data tables by supporting SQLCMD…
- Supports column filtered static data tables in the SCA plugin in SSMS
-
90 votes
Robert
supported this idea
·
-
170 votes
Robert
supported this idea
·
-
633 votes
Hi,
We just added this capability to Flyway, which is our x-database, x-OS cloud- and Git-first Database DevOps solution for versioning and deploying database changes. You can learn more about this feature in Flyway at https://documentation.red-gate.com/fd/working-with-data-138347109.html#Workingwithdata-Controllingstaticdata.
You can also import your SQL Source Control repos into Flyway while keeping your Git history. Learn more about moving to Flyway and importing your project at https://documentation.red-gate.com/fd/transitioning-from-other-redgate-tools-164167855.html.
If you have any questions, please comment below or reach out to us at DatabaseDevOps@red-gate.com.
Thank you!
Stephanie Herr
Product Manager - Database DevOps
Robert
supported this idea
·
-
215 votes
Robert
supported this idea
·
-
346 votes
Robert
supported this idea
·
-
477 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…
Robert
supported this idea
·
-
215 votes
Robert
supported this idea
·
please, check out (it's for SQL Prompt=: https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/32271289-support-for-microsoft-sql-operations-studio