Settings and activity
17 results found
-
99 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
·
-
300 votes
SQL Prompt for Azure Data Studio is now in public preview!
The aim of this public preview is to learn from the ADS community about how SQL Prompt can enhance your developer experience, adding improvements and new features based on your feedback.
With SQL Prompt, you can use an extensive collection of code snippets to write your SQL code quickly and efficiently. You can also keep your code consistent using the powerful formatting capability, with the ability to customise the applied style to suit your preferences.
We’d love to hear your feedback. You can get in touch with the team either via the new SQL Prompt in ADS forum: https://forum.red-gate.com/categories/sql-prompt-in-ads or email us at sqlprompt.in.ads@red-gate.com.
Get started with SQL Prompt for Azure Data Studio now. Download it here: https://download.red-gate.com/EAP/SQLPromptADS.zip
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?
-
57 votesBlaž Dakskobler
supported this idea
·
-
46 votesBlaž Dakskobler
supported this idea
·
-
100 votesBlaž Dakskobler
supported this idea
·
-
225 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
·
-
344 votesBlaž Dakskobler
supported this idea
·
-
76 votesBlaž Dakskobler
supported this idea
·
-
636 votes
Hi everyone. I have merged some User Voice items on this topic of “filtered” static data, as there was significant overlap. I want to share our current guidance on handling scenarios where you need to version a subset of the columns and/or rows in the table.
With SQL Source control, the best option at this point is to use a post-deployment script for this purpose.
SQL Source Control introduced pre- and post- scripts in v6.3.
A post-deployment script gives you a good amount of flexibility over exactly which rows or columns of data you want to include in your project. Example post-deployment scripts for static data are 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…
Blaž Dakskobler
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…
Blaž Dakskobler
supported this idea
·
-
153 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).