179 results found
-
Migrations support for Git/Mercurial
It seems that right now migrations only support SVN, TFS and Vault - none of which I'm willing to use anymore. Please consider prioritizing support for Git/Mercurial.
935 votesI am delighted to let you know that this is now released! Migrations support for Git/Mercurial is available – out of beta – in SQL Source Control 5.
If you’re new to SQL Source Control, you can try it out free for 28 days by downloading it from http://www.red-gate.com/products/sql-development/sql-source-control/.
If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.
You can see Migrations examples and tutorials here: https://documentation.red-gate.com/display/SOC5/Migration+script+examples
Thank you for your continued support, and please let us know if you have further feedback on this capability, or any others, in SQL Source Control!
-
Don't refresh the commit/get latest automatically
Having an option to calculate/determine the synchronizing between source control and local objects can be triggered with a button action rather than automatically starting this process when the source control tab is in focus.
317 votesAs of SQL Source Control 6.3.2, there is an option 'DisableAutoRefresh' to disable automatic refresh of the commit and get latest tabs. See https://documentation.red-gate.com/soc6/troubleshooting/refresh-in-commit-and-get-latest-tabs-takes-a-long-time for more details. Please get in contact if you have any additional feedback on this issue.
-
Make it faster!!!! Improve Performance!!!
Oog, each commit is like five minutes. Neither standard commits of source code (same SVN server) nor redgate SQL Compare actions (same local database server) take that long!
Keywords: Performance, Speed, Fast
312 votesWe have been doing a lot of work on SQL Source Control lately. We’ve recently improved performance when you link a database, go to the commit and get latest tabs (especially subsequent visits where we can rely on data being cached), and when selecting/deselecting all on the commit and get latest tabs.
If you are still experiencing performance problems, please make a new suggestion that is very specific to what you would like us to work on. Is it a specific step in the commit process that is taking a long time? Is it viewing history that is taking a long time?
We’ve also started to work on this suggestion, Don’t refresh the commit/get latest automatically, https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/462220-don-t-refresh-the-commit-get-latest-automatically, which will also help with performance.
Contact support@red-gate.com if you can share your database schema with us for performance testing purposes.
If you are experiencing problems with server load, please see http://documentation.red-gate.com/display/SOC33/Changing+or+disabling+the+database+polling+interval…
-
Exclude objects from versioning (svn:ignore)
As it is possible to exclude some files from SVN using file source control it would be great to remove some objects that we do not want to version - for example test procedures or users.
261 votesObject Filtering now appears in SQL Source Control version 2.2!
For more information about the release, please see:
-
Source Control Data (Data folder is blank)
would be awesome if it scripted the data as well
250 votesSQL Source Control v2.0 is now available with support for source controlling your static lookup data from within SSMS. For more details, see http://www.red-gate.com/MessageBoard/viewtopic.php?t=12947.
If you’ve been using SQL Data Compare Pro to source control your data in the “Data” folder, then please contact support@red-gate.com to keep your history.
If you need any advanced features, like only source controlling a subset of columns or limiting the rows with a WHERE clause, then you will need to continue to use SQL Data Compare Pro, http://www.red-gate.com/help/SourceControlData.html.
-
TFS - Exclusive Checkout / SVN - Lock
It would be really nice if there was a way to checkout or lock db objects so that I know that I'm the only person working on this object and I will not experience any conflicts when I go to commit the object.
242 votesWith SQL Source Control 4.0, we have introduced our new Object Locking feature!
This feature allows users to lock the SQL object directly on their database server, meaning other users on the same server cannot make changes until you finish you work and release the lock.
-
Support GIT hosted under TFS
We use GIT hosted under TFS in order to use Windows authentication to protect the GIT repositories.
SQL Source control does support a local copy of the GIT repository but remote Push and Pull fail in SQL Source Contrtol 5 because it cannot handle the login dialog needed to get to GIT
240 votesSQL Source Control 7 has now been released. In this version, SQL Source Control now uses the Git command line for all its Git interactions, which means it will support any Git authentication method that the command line supports. This includes TFS Git.
You will need to ensure that you have Git.exe available in your system path – the easiest way to do this if you don’t already have Git installed is to download Git for windows (https://git-scm.com/download/win)
-
Create migration script without changes to any database objects
It would be great if you could add just a migrations script to your source control without any related change to any object in the database. This would be very use ful when tyou have tabel A with column 1 and 2 and i column 2 you want to replace all 'A' with 'a' or something.
202 votesI am delighted to let you know that this is now released! You can now create migrations scripts even without schema changes.
If you don’t have SQL Source Control installed, you can download it from http://www.red-gate.com/products/sql-development/sql-source-control/.
If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.
You can see other Migrations examples and tutorials here: https://documentation.red-gate.com/display/SOC5/Migration+script+examples
Thank you for sticking with us while we worked on this, and please keep the feedback coming!
-
Support Multiple instances of SSMS
It would be really handy to support mulitple instances of SSMS, especially for multi-monitor people.
173 votesYesterday we released SQL Source Control 3.5, which includes support for multiple SSMS instances. Thank you to everyone who tested the beta.
Please check for updates to install. Full release notes on http://documentation.red-gate.com/display/SOC3/SQL+Source+Control+3.5+release+notes
-
Support merge / branch
I want to be able to work with more then one database, I want to have database for each developer that are all branches of the "trunk" db.
156 votesWe now support branches from your source control system. You should be able to branch in your source control system and then link a database directly to that branch.
Please contact support@red-gate.com if you have any problems or post a new suggestion for more specific features that you’d like us to implement around this, https://redgate.uservoice.com.
Thank you!
Stephanie M. Herr :-)
SQL Source Control Product Manager -
149 votes
This is now available in the full v2.1 release, http://www.red-gate.com/messageboard/viewtopic.php?t=13147.
NOTE: If you were using the EA, you will need to clear your LinkedDatabases.xml and TableDataConfigs.xml files and re-link your databases. These are found in
localappdata\Red Gate\SQL Source Control 2 -
Capitalization Change as Name Change
In a case-INsensitive collation, I changed the name of a stored procedure to fix a capitalization issue. This was first detected as a change (displayed the blue dot on the procedure and hierarchy in Object Explorer) but then when I went to the Commit Changes window and clicked the Refresh button, nothing appeared, and the blue dots disappeared.
Even though my data collation is not case sensitive, I would have expected this to be recognized as a name change.
Using version 1.1.3.4 connected to a Fortress 2.0.x repository.
120 votesOur latest Frequent Update supports detecting case differences in your database objects. The setting can be enabled through an edit to your Comparison Options (please see the documentation for details on this). If you’re not currently on our frequent updates channel, you can find out more here: http://documentation.red-gate.com/display/SOC3/Turning+on+Frequent+Updates
-
On a shared model, the Changed By column says unknown for some uncomitted changes on the Commit List
When I try to commit changes it says unknown user. I believe it is very important to be able to track who's making what changes.
112 votesIn v3.1, we store user information when an object changes so you don’t see “unknown” on the commit list for changes on a shared model. Details are at https://documentation.red-gate.com/display/SOC32/Logging+changes+to+shared+databases
-
Diff or compare versions of an object
I want to be able to diff/compare my db object to the previous version so I can see exactly what I changed. This would allow me to view differences between my current version and the previous version. I also want to be able to select which version I diff/compare the object to so I could see changes between any 2 versions.
109 votesSQL Source Control will now let you compare two revisions in the History dialog through SQL Compare
-
Add Git support
I know that svn and TFS support are important but I really hope you add Git support. Git is really taking off and I think we will be switching over at some point so Git support is key for us.
98 votesThe new 2.0.3 Early Access build now supports source controlling your databases with Git.
To get the new Early Access release please visit the following link:
https://www.surveymk.com/s/SqlSourceControl_EapSignup
Please note that we don’t support accessing the history directly from within SSMS when using Git.
-
Add SSH key support for push/pull to remote Git repository.
When using the 'Push to remote Git repository' feature in SC 4.1.8.41, add functional support for remote Git repositories that use SSH keys for authentication.
89 votesSQL Source Control 7 has now been released. In this version, SQL Source Control now uses the Git command line for all its Git interactions, which means it will support any Git authentication method that the command line supports. This includes SSH support. You’ll need to make sure you have your SSH key correctly configured for the Git command line to use.
You will need to ensure that you have Git.exe available in your system path – the easiest way to do this if you don’t already have Git installed is to download Git for windows (https://git-scm.com/download/win)
-
Mercurial support as source control system
Currently there are only choise of SVN and TFS but I think that support of the Mercurial would be really convenient.
86 votesThe new 2.0.3 Early Access build now supports source controlling your databases with Mercurial.
To get the new Early Access release please visit the following link:
https://www.surveymk.com/s/SqlSourceControl_EapSignup
Please note that we don’t support accessing the history directly from within SSMS when using Mercurial.
-
Migrations support for Perforce
Please can we have migrations functionality for Perforce SCM
72 votesI am delighted to let you know that this is now released! You can now create migrations scripts with Perforce, using the working folders option in SQL Source Control.
If you don’t have the tool installed, you can download it from http://www.red-gate.com/products/sql-development/sql-source-control/.
If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.
You can see other Migrations examples and tutorials here: https://documentation.red-gate.com/display/SOC5/Migration+script+examples
Thank you for sticking with us while we worked on this, and please keep the feedback coming!
-
SVN - Show Log (TFS - View History)
To have a tab that would simply grab and display the Log/History would be invaluable. This would be a fairly simple addition I would think.
71 votesShow history is now available as of v1.1.0.19. Please use Help > Check for Updates on the SQL Source Control tab within SSMS to make sure you have the latest version.
Thank you!
-
It would be helpful if Source Control showed which branch is checked out currently.
Before every commit I have to check in git if the selected branch is the appropriate. It's important and it would be easier, if SQL Source Control showed it.
67 votesAs of SQL Source Control version 5.6.1, the Git branch name is now displayed just above the commit/apply changes buttons.
- Don't see your idea?