I would like to know if there is a script for the SVN version database that will not provide conflicts when several developers try to make changes at the same time.
My team and I used changecripts to increase the version number of the schema (it looks like this solution: http://odetocode.com/blogs/scott/archive/2008/02/02/versioning-databases-change-scripts.aspx ).
This is a pretty good solution, but its main drawback is that conflicts can occur when several developers try to commit a script change with the same schema number - this is not only a simple SVN conflict, but also requires users with this conflict to manually change the database table with schema versions, revert their changes to db, change script file numbers to have all db updates. Can these obstacles be avoided? I mean only technical solutions, but maybe there is a better way to organize this task? Any ideas?
Rails solved this exact problem by using a timestamp instead of an incremental version number. The chances of two users creating new versions of circuits in one second are pretty low.
Some of these methods + links may help you.
From SO:
SQL Server Database Versions
Mechanisms for tracking database schema changes
Methods
http://www.jilles.net/perma/2003/10/17/database-versioning-techniques/
http://martinfowler.com/articles/evodb.html