Settings and activity
4 results found
-
11 votes
An error occurred while saving the comment 
Mary Hamlin
shared this idea
·
-
15 votes
An error occurred while saving the comment Mary Hamlin
commented
i was just going to add this suggestion myself, but i guess i will just vote for yours. :)
Mary Hamlin
supported this idea
·
-
79 votes
Kendra
responded
An update for users on the status of this suggestion:
An ‘object locking’ feature was added to SQL Source Control following the creation of this item which can helps users working in a shared database environment not write over each other’s changes.
This may help prevent accidental commits in some cases, as there is a “Locking” tab which allows users to see which other users are working on specific items.
Locked items are still eligible to be committed, however, and there are cases where users will want to commit an item — perhaps to a specific branch in source control which is not ready to deploy — even if the item in the database is locked.
We have found at Redgate that the easiest way to enable alignment with distributed source control systems such as Git is to empower users to use dedicated development databases rather than shared databases. Tools…
An error occurred while saving the comment Mary Hamlin
commented
Completely agree. We have a lot of sloppy developers who will most likely just check in everything when committing instead of selecting only the items that they changed themselves, potentially checking in objects that aren't ready for deployment yet. I think this is a big flaw in SSC at the moment. Also, on a related note, it would be nice if you could right-click on an object and commit the changes for just that object (which could help to alleviate some of the problems with accidental check-ins), or at a minimum have the object that you right-clicked show up as checked in the commit tab.
-
7 votesMary Hamlin
shared this idea
·
Unfortunately the SCP project stores the content of the SSC filter at the time that you save the project instead of a flag or something to indicate that the comparison should use the SSC filter. The down side of this approach is that if your SSC filter changes, the filter in the project file will still reflect the previous value. As we are using the SCP command line to run our comparisons, so it will make, which will make automation/continuous integration impossible.