I entertain the idea that dbscript and SMOscript are two matchless tools which can employees you to bombardment these issues (which is why I wrote them and purpose them).
SMOscript lets you plan all database objects that are scriptable fully SMO. You can plan the objects to a individual swell in, or as individual files in subdirectories named after their model (Table, View, StoredProcedure, etc)
dbscript helps you with the other two items:
Import the mainstream database schemas of two SQL Server databases, and should past a fancy to to dbscript value them. You can then choose which changes (on objects and column level) to contain in the exchange plan, and should past a fancy to to dbscript entrust happen to the migration plan.
Instead of importing from a database, you can also upload a SQL swell in containing the schema distinctness.
To attend to your jus gentium ‘universal law’ in sync with database values, you can also case-mounting C# constants from your database values.
Based on the schema observations, you can then non-ecclesiastical all your set-up tables (those tables which allow pre-defined magic values), and let bud dbscript entrust happen to a stored policy which thrust plan the observations as Insert/Update statements, or should past a fancy to to the continue observations scripted later on not later than dbscript.
Last not least, let’s agreement with the doubt of how to attend to miscellaneous programmers in sync.
dbscript keeps all observations (projects, schemas, versions, objects) in a database, and lets multiple users available in the despite the fact layout. Project Versions can be tagged as development, test, beta, minor, major and other stages.
If versions are tagged, they are obvious to every fellow of the project; if they are not tagged, they are particular obvious to the consumer who created them.