Settings and activity
9 results found
-
38 votes
We’re looking at improvements to tab history later during 2019 so will review this suggestion.
Interested in demand, so do vote on the suggestion if you would find it useful.
Michael Hotek
supported this idea
·
-
13 votes
An error occurred while saving the comment -
58 votesMichael Hotek
supported this idea
·
An error occurred while saving the comment Michael Hotek
commented
I'd agree that this is a mess. I have 1 workspace already on my machine that has our entire TFS structure pulled into it. I then hook up SQL Source Control and I suddenly have 148 additional TFS workspaces created on my machine (74 databases). Every database I add to source control produces 2 more workspaces. As a TFS admin, this is a ridiculous mess.
-
135 votes
Hi – this request was closed when the ‘TFS work items’ feature was released. http://documentation.red-gate.com/display/SOC3/Committing+changes
However, we’re still hearing about this enough that I’d agree with commenter Ben: it should be reopened.
We will continue to gauge interest here on UserVoice. Please do tell us more in the comments about what you expect to be able to do with Work Items in SQL Source Control.
Michael Hotek
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.
Michael Hotek
supported this idea
·
-
215 votesMichael Hotek
supported this idea
·
-
189 votes
While SQL Source Control provides a way to view object history, it does require additional tooling to update your database to a specific version from history.
We currently have documentation on how this works here: https://documentation.red-gate.com/soc/common-tasks/update-to-a-revision-from-source-control
Michael Hotek
supported this idea
·
-
480 votes
Thank you everyone for your comments and votes on this over the years. While I don’t have a 100% full resolution for this suggestion, I can sum up our current recommendations here. Continued feedback is very welcome.
Our current recommendation is to use the post-deployment script feature of SQL Source Control (released in V6.3) to manage SQL Server Agent jobs.
An example script for this is here: https://documentation.red-gate.com/soc/common-tasks/working-with-pre-post-deployment-scripts/create-sql-server-agent-job
As some commenters in this thread have alluded to, it is possible (and sometimes very common) for SQL Agent jobs to have steps that touch multiple databases on a single SQL Server Instance. For this reason, some customers prefer to create a separate database for instance-level management and objects (sometimes named DBA or similar) and choose to manage things like linked servers and SQL Agent jobs with the post-script associated with that database.
This separate-database architecture also makes sense if the jobs…
Michael Hotek
supported this idea
·
-
36 votesMichael Hotek
supported this idea
·
I'm voting for option 2. I want to be able to pin/unpin tabs so that they don't get removed even if I select the "Remove tabs older than..." option. This allows me to preserve tabs that I use very frequently without having to unbury them by manually removing 100+ other tabs which were more recently opened.