Settings and activity
15 results found
-
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
Adam Hafner
supported this idea
·
-
103 votesAdam Hafner
supported this idea
·
-
6 votesAdam Hafner
shared this idea
·
-
72 votesAdam Hafner
supported this idea
·
-
34 votes
It would be great if you could let us know more about how you’d use a Prompt API / command line version of Prompt.
What problems are you having without it?
How are you getting around those?
How would this make your work better?Adam Hafner
supported this idea
·
-
9 votesAdam Hafner
shared this idea
·
-
22 votesAdam Hafner
supported this idea
·
An error occurred while saving the comment -
53 votesAdam Hafner
supported this idea
·
-
75 votesAdam Hafner
supported this idea
·
-
8 votesAdam Hafner
shared 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.
Adam Hafner
supported this idea
·
-
3 votesAdam Hafner
shared this idea
·
-
32 votesAdam Hafner
supported this idea
·
-
29 votesAdam Hafner
supported this idea
·
An error occurred while saving the comment Adam Hafner
commented
I would also add the following recommendation for this enhancement to include the ability to assign shortcut keys to switch the connection context of an SSMS tab. That way you could reduce the clicking even more.
-
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…
Adam Hafner
supported this idea
·
Martin, I have actually suggested this same functionality in another suggestion if you wanted to put your votes on my post instead it might get more attention...just a suggestion. :)
Here's the link...
https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/13484127-sum-selected-columns