The answer to your question depends on which database you are using. I think VSS integrates with SQL Server. You could have a policy where any structural changes need to be made using SQL commands, as opposed to the graphical interface. The SQL files could be part of and source control software. If you have SQL Server 2005, you could also track all structural changes using the new DDL triggers. There is plenty of sample code around that does this. RedGate SQL Compare can be scripted to make snapshots and to determine differentials against MS SQL Server databases.
One thing I do is generate the SQL script for the entire database and save it into a dated file that is inside of the project directory. That way, when I do extended searches from within HomeSite, I am also searching though the database schema. Having the SQL code in the project directory also means that it is backed up and versioned to some degree. It is not true version control, but it is good enough for me. -Mike Chabot On 10/23/06, Neil Middleton <[EMAIL PROTECTED]> wrote: > Has anyone any experience with source control of SQL databases (even better > using svn). If so, how do you handle it? What sort of scripts do you have? > How do you deal with updates to schemas/data? How do you deal with existing > data in the target database at release? > > Anyone? > > -- > Neil Middleton > > Visit feed-squirrel.com > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:257820 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
