Settings and activity
8 results found
-
18 votes
Simon
supported this idea
·
-
189 votes
While SQL Source Control provides a way to view object history, it does require additional tooling to update your database to a specific version from history.
We currently have documentation on how this works here: https://documentation.red-gate.com/soc/common-tasks/update-to-a-revision-from-source-control
Simon
supported this idea
·
-
210 votesSimon
supported this idea
·
-
39 votesSimon
supported this idea
·
-
76 votesSimon
supported this idea
·
-
11 votesSimon
supported this idea
·
An error occurred while saving the comment -
125 votes
An error occurred while saving the comment Simon
commented
This provides a great way to standardise code styles; trying to clean up a legacy database prior to adding it to Source Control could be a monumental task, but if the option were there to automatically apply the rules in SQL Prompt (which ideally would already be shared by the developers anyway) would mean the entire code base could easily be standardised.
It's 'one less thing to have to remember' too.
Simon
supported this idea
·
-
2 votes
An error occurred while saving the comment Simon
commented
I am using Mercurial and this is an issue for me too
Simon
supported this idea
·
It would be quite nice to be able to specify a database level to validate against too. For example 2008 needs semi-colons before CTEs but 2005 doesn't.
Sometimes when moving a database between servers I first ensure there are no invalid objects that will prevent SQL Compare from being able to generate the new database, currently I have to run SQL Compare, find an issue and fix it then repeat until there are no more issues. If Find Invalid Objects could detect those 'potentially invalid objects' that would be good