Settings and activity
5 results found
-
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…
Vincent Salard
supported this idea
·
-
476 votes
Thank you everyone for the suggestions and votes for this over the years.
I’d like to surface up a workaround for the “linking” problem which is mentioned in the comments. For the use case of easing pains around environment setup with a large number of databases, we have had customers find success using code based off Alessandro Alpi’s blog post: https://alessandroalpi.blog/2016/06/28/automatically-link-databases-to-red-gate-sql-source-control/
I do understand that this is a broader issue and hear that many of you also want command line or API support for the product in general.
If there are specific scenarios or workflows that would be useful to automate for you, this feedback is also very useful, and if you have details on the type of VCS you use and the workflow (such as a branching model) that it would fit in to, that would be very helpful for us to hear as well.
Vincent Salard
supported this idea
·
-
135 votes
Hi – this request was closed when the ‘TFS work items’ feature was released. http://documentation.red-gate.com/display/SOC3/Committing+changes
However, we’re still hearing about this enough that I’d agree with commenter Ben: it should be reopened.
We will continue to gauge interest here on UserVoice. Please do tell us more in the comments about what you expect to be able to do with Work Items in SQL Source Control.
An error occurred while saving the comment An error occurred while saving the comment Vincent Salard
commented
Hi Stephanie,
Could you give a feedback concerning the TFS WI integration improvements ?
Thx in advance,
Rgds,
Vincent.Vincent Salard
supported this idea
·
-
5 votesVincent Salard
shared this idea
·
-
3 votesVincent Salard
supported this idea
·
An error occurred while saving the comment Vincent Salard
commented
This is indeed source of mistakes since case sensitivity is more related to Unix world. Pretty disturbing at first shot.
Hi Tanya,
I was already aware of the parse trick but it only applies on standard WI status. A real UI integration makes more sense when we build our own status (without talking about WI lookup). I just wanted to know if it was near to be released or if a deadline was expected.
Thx for your feedback,
Regards,
Vincent.