Settings and activity
4 results found
-
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 
Anonymous
supported this idea
·
-
207 votesAnonymous
supported this idea
·
An error occurred while saving the comment Anonymous
commented
I would frame this as modify change management to allow GIT branch management. Currently I have to go to the command line and create and checkout a branch, then go back to CM and do my changes. I always have to remember to remove my local branch from the command line and pull master after pushing my changes to remote. Not a good experience for GIT beginners.
-
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…
Anonymous
supported this idea
·
-
18 votesAnonymous
supported this idea
·
I love Redgate toolkit and SQL Source Control, but would like to integrate it into other tools and processes. Creating a CLI or Powershell (PS) module that allows users to check a database for changes and check in those changes from the command line would be awesome. I am already going to PS to create branches and it would be nice to just check in my change while I'm there.
I would also love to see the ability to manage DB connections for SSMS, VS and VSCode in one location.