SQL Changeset and Subversion

bconlon

Any plans to support SQL Changeset on Subversion?

David Atkinson

Subversion is one of the top three source control systems so we will definitely consider this in our future source control plans. I can't confirm when this will happen, but if you ping me in late Q1, our plans should be much clearer.

Kind regards,

David Atkinson
Product Manager
Red Gate Software

Michelle T

In general you should be able to just use SQL Compare (without needing SQL Changeset) on databases kept in Subversion repositories, getting the latest version before you load SQL Compare to do the comparison and committing the changes after you're happy with them in your usual way.

SQL Changeset is designed to work with the 'check out / edit / check in' source control model (rather than 'edit /merge / commit' which is the usual way of using Subversion), where you need to check out the files before SQL Compare performs the synchronization.

If you don't need to check out the files before editing them, you don't need SQL Changeset (which mostly just interfaces with Compare to ensure files are checked out during the synchronization process - the only other thing it can do is make sure the latest version is acquired before the comparison, and remind you that files need committing, which aren't really worth such a heavyweight solution on their own).

David Atkinson

Michelle makes an excellent point. If you read http://www.sqlservercentral.com/article ... ols/61769/ there is an example of how SQL Compare can be used with Subversion without the need for SQL Changeset. The fact that this article refers to Subversion is arbitrary - the theory applies to any source control system. SQL Changeset is nothing but a tool that auto checks out files on your behalf. Many source control tools don't require this 'assistance'.

David Atkinson
Red Gate Software