Settings and activity
88 results found
-
5 votes
In v2.2, which is expected to be released in the next few weeks, we’ve implemented Object Filtering, which allows you to specify which objects to inlcude/exclude for source control. Therefore, you could link a database and set up a filter so that only the tables/procedures your interested in for your project would be source controlled. Would this help?
You can get the v2.2 Release Candidate at http://www.red-gate.com/messageboard/viewtopic.php?t=13668 to try this out.
paul price
supported this idea
·
-
3 votes
-
6 votes
If you close the SQL Source Control tab, then it will NOT show up the next time you start SSMS.
paul price
shared this idea
·
-
215 votes
An error occurred while saving the comment paul price
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
An error occurred while saving the comment paul price
commented
I'm going to agree with Neil. This functionality should be in THIS tool, and not rely on the use of another RedGate tool (even though I have it).
paul price
supported this idea
·
-
1 vote
In a future version, we hope to have the ability to browse a repository so that it doesn’t have to be manually entered. This topic is listed at http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/539431-browse-to-a-svn-repository-instead-of-manually-typ.
-
3 votes
Did you know? The “Next” button at the top of the diff pane will jump to the next difference in the script. This may help you jump right to where the first change is for now.
-
12 votespaul price
supported this idea
·
I am always working with several versions of a database. At a minimum, I have the following:
- Local (personal working copy on my machine)
- Dev (shared by all developers on my project on a shared server)
- Q/A (used by the test team on a shared server)
- Prod (the current production version on the production servers)
I would love to be able to have all copies of the database (Local, Dev, QA, Prod) open in SSMS and be able to determine what schema version is running on each. This could be via a right-click option or some other visible cue. I would also need to be able to report on this schema version number.