Settings and activity
9 results found
-
29 votes
sheldonhull
supported this idea
·
-
42 votes
An error occurred while saving the comment -
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…
An error occurred while saving the comment sheldonhull
commented
I've had management ask for this before. This would make it much more flexible for our usage.
sheldonhull
supported this idea
·
-
476 votes
Thank you everyone for the suggestions and votes for this over the years.
I’d like to surface up a workaround for the “linking” problem which is mentioned in the comments. For the use case of easing pains around environment setup with a large number of databases, we have had customers find success using code based off Alessandro Alpi’s blog post: https://alessandroalpi.blog/2016/06/28/automatically-link-databases-to-red-gate-sql-source-control/
I do understand that this is a broader issue and hear that many of you also want command line or API support for the product in general.
If there are specific scenarios or workflows that would be useful to automate for you, this feedback is also very useful, and if you have details on the type of VCS you use and the workflow (such as a branching model) that it would fit in to, that would be very helpful for us to hear as well.
An error occurred while saving the comment sheldonhull
commented
Unfortunately, Chris's solution was not workable for us. I believe this is still a need.
An error occurred while saving the comment sheldonhull
commented
This issue still seems to exist for 2013. Any updates?
An error occurred while saving the comment sheldonhull
commented
@Chris, why won't the working folders come through, when I see them in the XML file?
sheldonhull
supported this idea
·
-
7 votessheldonhull
shared this idea
·
-
16 votes
An error occurred while saving the comment sheldonhull
commented
I agree. Modal focus on this window makes it difficult to use.
sheldonhull
supported this idea
·
-
4 votes
-
5 votessheldonhull
shared this idea
·
-
345 votessheldonhull
supported this idea
·
I agree. The modal window means I never use it. I'd love a summarize script option that parsed in the background so I could use it to navigate to sections. It doesn't provide any usability when it's not a window I can move to the side.