Settings and activity
17 results found
-
40 votes
Claudio supported this idea ·
-
68 votes
An error occurred while saving the comment -
205 votes
An error occurred while saving the comment The same behaviour as F12 shortcut from Sql Prompt would be great
-
99 votes
-
339 votes
-
216 votes
An error occurred while saving the comment What's the point of have a "User Voice" section if the most upvoted suggestion was not considered after so many years?
-
33 votes
-
159 votes
-
44 votes
-
50 votes
-
146 votes
-
37 votes
-
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…
-
18 votes
-
83 votes
-
18 votes
-
125 votes
SSMS has serious memory limitations when dealing with large scripts. Making smaller scripts is a must.