Settings and activity
17 results found
-
102 votes
Kendra
responded
As David mentioned in the comments, we currently recommend Flyway to help version changes for Snowflake.
Flyway doesn’t help with authoring or scripting changes, but it does provide a framework and guidelines to consistently version your changes in a deployable fashion that’s suitable for automation.
https://flywaydb.org/documentation/database/snowflake
Thank you for the suggestion and comments, as well those who have voted.
Blaž Dakskobler
supported this idea
·
-
5 votesBlaž Dakskobler
shared this idea
·
-
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
Blaž Dakskobler
supported this idea
·
-
29 votes
An error occurred while saving the comment Blaž Dakskobler
supported this idea
·
-
61 votesBlaž Dakskobler
supported this idea
·
An error occurred while saving the comment Blaž Dakskobler
commented
Hi, what's the status here?
-
58 votesBlaž Dakskobler
supported this idea
·
-
49 votesBlaž Dakskobler
supported this idea
·
-
102 votesBlaž Dakskobler
supported this idea
·
-
226 votes
We've had a few requests for supporting MERGE statements - https://redgate.uservoice.com/redirect/suggestions/3100622. Would MERGE help this or are you still looking for IF EXISTS on INSERTS? If you'd like to chat about this, please reply.
Blaž Dakskobler
supported this idea
·
-
42 votesBlaž Dakskobler
shared this idea
·
-
14 votesBlaž Dakskobler
supported this idea
·
-
346 votesBlaž Dakskobler
supported this idea
·
-
76 votesBlaž Dakskobler
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
Blaž Dakskobler
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…
Blaž Dakskobler
supported this idea
·
-
154 votesBlaž Dakskobler
supported this idea
·
-
79 votesKendra
responded
An update for users on the status of this suggestion:
An ‘object locking’ feature was added to SQL Source Control following the creation of this item which can helps users working in a shared database environment not write over each other’s changes.
This may help prevent accidental commits in some cases, as there is a “Locking” tab which allows users to see which other users are working on specific items.
Locked items are still eligible to be committed, however, and there are cases where users will want to commit an item — perhaps to a specific branch in source control which is not ready to deploy — even if the item in the database is locked.
We have found at Redgate that the easiest way to enable alignment with distributed source control systems such as Git is to empower users to use dedicated development databases rather than shared databases. Tools…
+1
There's an implementation for this in SSMS Boost (community licence is free)... actually that's the only reason I have SSMS Boost installed.
@RedGate check out that implementation, there's some other nifty options (like opening a connection in object explorer / a new query window on SSMS startup ... can be set up per preferred connection).