Settings and activity
3 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.
Micky
supported this idea
·
An error occurred while saving the comment -
215 votesMicky
supported this idea
·
-
6 votes
We currently don’t have an option to pause polling in the tool, but you can confiugre an XML file. Please contact support@red-gate.com for details. This file would need to be set for each user.
You could also add a “Column Filter” in SQL Profiler’s Trace Properties’ Events Selection where “Application Name” is “Not like” “Red Gate%.” That should filter out the polling in your trace.
I hope this helps!
Micky
supported this idea
·
An error occurred while saving the comment Micky
commented
Or at least slow it down. Does it really need to connect every second? (I don't know how often it connects, but it seems like a lot!)
We would also like a way to automate the commands of SQL Source Control. Specifically, we have this situation.
1.) Each developer has their own instance of SQL Server with the same 8 databases.
2.) The developer can use SVN Switch to switch to the branch that they want to work on.
3.) The developer should be using the schema that goes with that particular branch.
As it is now, when we switch between branches, we have to go to each of our 8 DBs and do the following:
A.) Unlink it from where we were working
B.) Link it to the branch we are working in now
C.) Get Latest Updates to get things that don't exist but need to exist
D.) Undo changes to get rid of things that shouldn't exist.
It'd be great if we could automate A, B, C, and D for each of our 8 DBs. I'm looking into using AutoIT for this, but haven't started that process yet. I'd prefer something more "supported". We could possibly use SQL Compare for some of this, but the feature that we really want is the static data feature of SQL Source Control. That let's us version our lookup tables.
With the ability to automate this, we'd save a TON of time and prevent mistakes when switching between branches.