Settings and activity
2 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.
Carlos Gonzalez
supported this idea
·
-
8 votes
An error occurred while saving the comment An error occurred while saving the comment Carlos Gonzalez
commented
This is a great idea for us too. We are constantly switching databases but each developer like me only has ONE database. It's also frustrating because we are not able to navigate to another database when waiting for the refresh of our own database (and these refreshes are taking way longer than on previous versions).
Carlos Gonzalez
supported this idea
·
It could be as easy as placing a lock to the right of the database name (which shows on the top left for me in SQL Source Control). So once it's "locked" it will not change based on SSMS active object selection (basically the lock disables the code you have currently running on the selection event).