SQL Source Control
Thank you for evaluating SQL Source Control. Your feedback will impact what we do next!
-
SQL Source Control / Red Gate Configuration Database
I think it would be nice if SQL Source Control (or Red Gate in general, in case it is useful across other products) had its own config database. This would be the one location to store all information related to this product, instead of storing some information in a database (v3.1 RG_AllObjects table), some in .xml config files, and some as extended properties on the database.
I would much rather create one database (that I could specify on install, instead of having to go into a config file and change it from TempDB) that I could host of a single…
11 votes -
Bug (shared model): Tables with extended properties still highlighted after commit.
SSC 3.1.0.4829
SQL Server 10.50.4000
Shared modelAfter adding an extended property to a table the recognition and the commit work fine. But after having committed the changes the table will be remarked as having pending changes in the object explorer of SSMS. In the commit changes tab there are no changes to commit which is correct.
Maybe also extended properties with other objects are affected.
14 votes -
Can you provide an option to make the comments as mandatory when commit the changes
When committing changes to source control, Developer should enter the comments(This is our rule) for that I need to set the Comments as mandatory.
Now SQL Source control not have any feature to set the comments as mandatory.4 votes -
Commit portions of static linked data
It's only possible to check in entire tables when there is some data changes in them. I would like it to possible to check in/commit only selected rows instead of entire table.
We are a couple of developers that are using the database and while we are developing our different tasks we update our test database. When each task has a go to release we want it to be able to just check in that tasks specific alterations.
18 votes -
compare what I am about to check in against the previous check in
I see the changes to be checked in , these may have been done by other developers. I want to compare the changes about to be checked in against the previous version to see what changed before I check in.
7 votes -
accurev
I'm missing native support for AccuRev (http://www.accurev.com/) in the SQL Source Control product.
12 votes -
Option to store the "Version", "Linked to" and "Migration folder" in a file not the database
Currently Source Control information is stored in database extended properties in the database being source controled. This requires Alter Database. In production those of us who use RedGate for Source Control, do NOT have Alter database because only the sys admins have that. And they do not want to bother with RedGate as they are just acting as auditors not database developers in production. Other environments we have full rights, just not production. It would be great to have an option to store the "Version", "Linked to" and "Migration folder" in a file not in Extended properties in the database.
16 votes -
In the commit window, have a search field as in SQL Compare to locate item to commit
In the commit window, have a search field as in SQL Compare to locate item to commit
2 votes -
Cross database dependancies
SQL Source Control and SQL Compare should be able handle cross database dependencies in the same instance and should be able to generate a single migration script for both databases
3 votes -
Every database has its own Comments before Commit
I usually use the Comments feature of the Source Control in two ways:
1. The normal way, i.e. as the comment for a Commit
2. A note before "Commit". But, using it as a note is quite awkward because it will not stick with the database. When moving to another database, the note will become the note for current database.
I wish that the every database can have its own Comment to stick with before Commit so that it will not accidentally commit with the wrong comments.1 vote -
1 vote
-
UI defefect after unlinking SQL DB from VCS
DB was linked to SVN repository.
I needed to move its location (apparently not supported).
So I unlinked, planning to re-link in new location, disregarding history.
Once unlinked, the source control tab UI was messed up.
Close the tab, re-open, still messed up.
Disconnect the DB, reconnect, show the source control tab, still messed up.
Close SQL Management studio, restart, show DB, show source control tab, then finally it was OK again.Messed up = I could not see the any of the text on the setup tab that normally says "not linked... Link DB to source control..."
In its…1 vote -
Support SQL Server Management Studio 2012
Allow SQL Source Control to work on SSMS 2012, where SSMS 2008 and 2012 are both installed on the same machine
12 votes -
Bug with certain tables names
If you have 2 tables Config and Config_Data and wish to store static data for both of them then after you have committed successfully it comes back saying that that the Config is not committed and lets you commit it again. Each time incrementing the committed version but always saying there is a difference. It is most liely because you store the data scripts as <table_name>_data.sql and it is getting confused between the 2 tables.
1 vote -
4 votes
AdminStephanie
(Admin, Red Gate)
responded
If you right click on the object, you can show history to see the author, when it was done, what was changed, and the author’s comment.
-
1 vote
-
Excluding "starts with underscore" filters out all objects
I can find no guidance on filter patterns. We have a lot of "temporary" tables which start with an underscore. We've previously used object filters to exclude anything which starts with an underscore. This now excludes all objects in the database, presumably because it's using SQL wildcards. Is the filter syntax SSC uses specified anywhere?
2 votes -
cygwin git not work.
Cygwin git can not commit code.
1 vote -
ComparisonOptions.xml should be easily shared and checked-in for each project
Having to set up as described in the link below isn't very nice at all.
http://www.red-gate.com/supportcenter/content/knowledgebase/SQL_Source_Control/KB201202000521This should be a standard (easily-accessible) setting that you can have on a per-project basis (not a per developer basis) so that you don't have to worry about individual machines.
20 votes -
Bug. The Change Connection functionality within the SQL Editor is disabled by SQL Source Control.
When my connection is disabled in SSMS, I use the Change Connection functionality to reestablish it. With SQL Source Control installed, I can't because the Change Connection functionality is disabled.
1 vote
- Don't see your idea?