SQL Source Control
Welcome to the SQL Source Control feature suggestion list. Find out more information about SQL Source Control at http://www.red-gate.com/products/sql-development/sql-source-control/.
If you have any questions, need help or have found a bug in SQL Source Control, please review our support information http://redgatesupport.red-gate.com/home.
To get new features, performance improvements and bug fixes as soon as they’re available, you may want to turn on frequent updates: http://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates
-
Make SQL Source Control external to SSMS
Make SQL Source Control external to SSMS like SQL Compare. This would allow the developer to use what ever IDE they want to and still commit the changes the same way. I would use SQL Compare to make changes, but it can't do everything SQL Source Control can. Mainly the migration scripts and the pre and post scripts.
11 votes -
Changing a data type used in a SP creates problems
When changing a data type used in a SP (e.g. add a new column to it and commit it). getting latest fails on other linked DBs. You have to drop the SP on the target DB.
The weird thing is that sometimes it works, but most of the times it doesn't. Not sure why the behavior is not the same all of the times...3 votes -
Use Visual Studio or VS Code as a merge tool.
Add support for manually merging changes in Visual Studio or VS Code instead of KDiff3 or Beyond Compare
6 votes -
migration scripts
When re-linking databases to source control, there is a warning message about loosing all uncommitted migration scripts, with only a OK/Cancel option. It's seems there should be an option for 'take me to the commit page' so that I can commit those scripts, then re-link.
2 votes -
Feature which should enforce user to lock the object before editing when administrator enables the restrictive policy for the users
Feature which should enforce user to lock the object before editing when administrator enables the restrictive policy for the users
If it is there it will be very much helpful for most of the development projects not testing and production.
4 votes -
Source Control Standalone instead of SSMS snapin
Source conrtol should be a standalone app not SSMS addin. When performing get latest or commits, on large environments and slow connections this can easily take 20 minutes during which a click anywhere else in SSMS restarts the get latest/commit process. The logical use of source control being a SSMS addon has been outlived.
58 votes -
Support Database Projects Referenced as Same Database in SSDT
Currently, when comparing an SSDT project using SQL Compare, it only loads the base project. If the project references another project as the same database (the standard workaround to the circular reference problem), the objects in the referenced project will not be compared. This can lead to changes being missed and deployments failing.
It would be nice if SQL Compare could follow the reference back and include the objects from the referenced database in the compare as well.
10 votes -
Do not allow to commit changes to an object that is locked
I don't see why is good this product if it's posible do commit to an object that is locked. If the object is locked this means that the user is editing it Then why allow to commit to this object
5 votes -
4 votes
-
When a user closes a session/SSMS it would be useful to have the user to prompted about any pending check-ins (shared db).
We use a shared environment, and if someone forgets to check something in, then the changes made appear as if from the next user to edit the item.
4 votes -
Syntax-aware comparison of revisions
Add an option/feature to actually parse the SQL ("Syntax aware") when comparing two different revisions, such that a change in just whitespace understands that the code is the same, even if the file(s) stored in SVN/other source control are different. Some people format things differently if they're not following standards in an org.
One "simple" way to do this would be the highly-voted option to use the SQL Prompt formatting engine to apply formatting to both revs and then see if there's a difference.
3 votes -
SQL Source Control - Filter
We are a shop that have multiple systems for clients that we managed from within a single database, using a separate Schema for each system.
I would like to be able to link a TFS database to a filtered list of objects (preferably) an entire schema but I could see where others might like just a subset of other objects.
If this is currently possible please let me know but I do not see a way to accomplish this without having a separate database for each system per client.
11 votes -
1 vote
-
Source Control - Changed by unknown
Problem:
Sysadmin role is required to see who changed a DB object. I am not permitted to have this role and I would imagine many devs are in the same boat. This means that when many objects have been checked-in by many users it is hard to pick out one’s own changes.
Solution:
Have an option when checking-in which adds a 1 line encrypted comment to the start or end of each object script. The comment would contain the username of the person making the check-in (and a control parameter like the time of check-in for instance)
This username can…18 votes -
Add filter option for filegroups
Add an option in the SSC filter to ignore differences in filegroup location as there might be multiple instances of a controlled database that have different filegroup configurations
6 votes -
support merging with ultracompare
I would like to see UltraCompare also supported as a Merge Tool.
5 votes -
Add Filter to Migration Scripts
Add Filter to Migration Scripts
When you go to create the migration script, you get to choose which commits are part of that script. It would be great to sort the migration script by the product descriptions or tags. When we have multiple commits to a database, and we might commit #project1 and #project 2 back and forth for a month, and instead of having to ctrl click through every other one, it would be great if we could group them together (or filter) and then generate the migration script easier.
5 votes -
Customize headers, footers and batch footers in migration script
I'm hard pressed to think of any corporation that would take a migration script and run "as is". You will at the minimum have some standard code or comment block to put at the top and bottom of a script.
For example, in our particular place, we check the DB version before running a script (header), and stamp a version on success / error handle (footer).
We also have special statement which we need to put after each batch (where the migration currently places a "GO").
Needless to say, having to manually do this is time consuming. So my suggestion…
5 votes -
On the "Get Latest" page, provide a way to globally un-check all objects
Can you please provide a way to "Uncheck" the entire list of objects on the "Get Latest" tab. I have 100+ objects ( Team of 6 Devs ) to get latest and 3 or 4 objects have issues, so I have to manually uncheck each of the 100 checkboxes and then check just the ones I think are ok to check in
1 vote -
prevent timeout on commit changes tab for larger db in shared database model
prevent timeout on commit changes tab for larger db in shared database model
6 votesThe timeout occurs when SQL Source Control runs a SQL query to find out which user made the changes that need to be committed, and the server takes too long to respond.
SQL Source Control 3.6.0 improves this situation, so that if a timeout occurs you can still go ahead with the commit. This version is currently available on Frequent Updates. To learn how to turn on frequent updates, see: http://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates
- Don't see your idea?