Currently SQL Source Control is crashing when SQL 2016-specific code is used, for example:
DROP TABLE IF EXISTS #input;
It should recognize this code since SQL Server 2016 works with it.14 votes
This is caused by the SQL Compare parser not understanding this syntax. The good news is the SQL Compare team are currently working on SQL Server 2016 parser support. Once this work is done and SQL Source Control is updated with the latest SQL Compare engine, I will update this request again.
History window should indicate the fact that some of the changes are covered by the migration scripts and provide the ability to view these scripts10 votes
We have been working on v2 of Migrations, which stores migrations scripts in a table valued function within the database. This table valued function appears in the history. An Early Access Release of SQL Source Control is now available and can be downloaded from http://documentation.red-gate.com/display/MV2.
NOTE: This is an Early Access Release and is not fully tested or functionally complete yet. It would be great if you could try it in a test environment and let us know about your experiences so we can fix any issues and try to make any updates you need before the full release.
Stephanie Herr :-)
SQL Source Control Product Manager
I'd like to see migration scripts support for PlasticSCM. Why isn't something that is written as a "plugin"? Plastic isn't supported out of the box, but it's a simple enough matter to make a config file for it. Why can't the same be done for migrations? Allow the end user to create a config file (perhaps requiring the use of regular expressions for history parsing) or some other such mechanism. It seems like this should be a relatively straightforward thing to be able to do (it would also allow the customers to create the support for any SCM system they use).
I'd like to see migration scripts support for PlasticSCM. Why isn't something that is written as a "plugin"? Plastic isn't supported out of the box, but it's a simple enough matter to make a config file for it. Why can't the same be done for migrations? Allow the end user to create a config file (perhaps requiring the use of regular expressions for history parsing) or some other such mechanism. It seems like this should be a relatively straightforward thing to be able to do (it would also allow the customers to create the support for any SCM system they…9 votes
Hello! We believe that this now works if you’re connecting to PlasticSCM with the working folder option in SQL Source Control. Before we close this request, though, we’re hoping that one of you with a real installation can check it out and let us know.
If you don’t have the tool installed, you can download it from http://www.red-gate.com/products/sql-development/sql-source-control/.
If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.
Thank you for sticking with us while we worked on this, and please keep the feedback coming!
on the conflict resolution screen, easier way to page down through lots of conflicts and 'take mine'
would be really nice on the conflict screen if you didn't have to click up on the row then move mouse down to option button way at bottom, 185 TIMES! If you could just select a range and say 'take mine' or page down with arrow key and hit an F key F1 mine, F2 Theirs...4 votes
Highlight 1 row, then click Ctrl-A to select them all. Then use “Keep Mine” or “Take Theirs,” which will apply to all the highlighted objects.
Can this work if I already have a VS Database project setup? Meaning can this work and interact with a VS Database project so that I can continue working on the actual db in SSMS, but the files get saved to the VS Db Project?210 votes
This is now available in the full release of SQL Source Control, http://www.red-gate.com/products/sql-development/sql-source-control, but it is still a beta feature.
SQL Source Control can link databases to the most recent version of Microsoft database projects (those folders containing a .sqlproj file).
It’s important to stress that this is a beta-quality feature, and as such it is only intended for experimental use. In particular, we are aware of some limitations regarding database-level extended properties, permissions and CLR assemblies. If you encounter these limitations or any other problems with this new SSDT compatibility, please let us know by using the Feedback link in SQL Source Control or contacting firstname.lastname@example.org.
I have seen no way on how to actually do a merge with SVN and mark as merged etc
We really need a more inutuitive way to merge the changes to SVN and vice versa. At the moment I am getting conflicts that I can't put into SVN because there is no way to say it has been merged, or even how to merge the changes.85 votes
We’ve released a version of this feature in SQL Source Control 3.5.
This version allows you to merge stored procedures using either Beyond Compare or KDiff3.
Do let us know what other objects it would be useful to have this feature on.
Please check for updates to install. Full release notes on http://documentation.red-gate.com/display/SOC3/SQL+Source+Control+3.5+release+notes
- Don't see your idea?