Settings and activity
32 results found
-
200 votes
Kendra
responded
While SQL Source Control does not currently provide a simple way to right click and ‘Undo’ static data changes on the ‘Commit’ screen as suggested, there is a workaround which may help some users.
If you wish to revert the static data in the table to a previous version which you have committed, you can do this by viewing the history of commits for the object in SQL Source Control, and then launching SQL Data Compare to update the database.
Please note that this workaround requires a license for Data Compare. More detail on how to do this are here: https://documentation.red-gate.com/soc/common-tasks/update-to-a-revision-from-source-control
SC
supported this idea
·
-
4 votes
SC
shared this idea
·
-
2 votes
SC
supported this idea
·
-
17 votes
An error occurred while saving the comment
SC
supported this idea
·
-
4 votes
SC
supported this idea
·
-
75 votes
SC
supported this idea
·
-
4 votes
SC
supported this idea
·
An error occurred while saving the comment
SC
commented
It looks like you guys have made a start on this idea with the new update icon in SQL Prompt. That's really cool. If you could make the rest of the suite the same way, and check for all updates from the same icon, that would be awesome! (It would save me a lot of time each time there's an update!)
SC
shared this idea
·
-
7 votes
SC
supported this idea
·
-
45 votes
An error occurred while saving the comment
SC
commented
This is close to my style too. Aligning the "AS" in SELECT clauses, then aligning that with the "ON" in the joins in the FROM clause too... the formatter has a lot of work to do to match my style, to be honest...
SC
supported this idea
·
-
25 votes
An error occurred while saving the comment
SC
commented
Yes, this would be insanely useful for me as well.
SC
supported this idea
·
-
14 votes
SC
supported this idea
·
-
20 votes
An error occurred while saving the comment
SC
commented
Absolutely! Can't believe this is something SQL Source Control can't do, it's a really major oversight on the part of the developers.
The fact that SSSC has actually in the past had bugs where if you check in a schema change at the same time as a data change nobody can do a get latest actually makes this worse.
SC
supported this idea
·
I've put this as an idea under one of the other products as well but supporting this one simply because it would be useful.
Also I definitely second Bob Vale's comment, that would be incredibly useful as well.