Database Under Source Control

[irasmith]

I have been doing some research on the matter and I think it is safe to say that no matter what source code control system you may be using, the one thing that doesn't fit in it directly is the actual database.

 

I have read some suggestions that you put the scripts that it takes to create the database, tables, view, stored procedures, etc. under source control instead. This does make sense to me and it is something that I am very willing to do.

 

My question on the matter is one of seeking the best approach to do it. By that I mean, would I have one large document file with all the t-sql commands for creating tables, a second document for stored procedures, etc. or would it be better to have a separate document for each table, stored prcedure, etc. treating them more like independent source files?

[PlausiblyDamp]

http://weblogs.asp.net/scottgu/archive/2006/06/09/VS-2005-Team-Edition-for-Database-Professionals.aspx may be just what you need (when in gets here).

[irasmith]

Thanks for the link and I had kind of guessed that is what that particular release would be suited for.

 

I am looking at something a little less 'intense' from the perspective of a fellow like myself using just the normal VS.NET 2005 Professional edition which has no source control system. I have been doing a lot of looking and I will most likely go the subversion route as my source code control solution. I really don't have the spare funds to purchase the VSS product at this time and my MSDN subscription is at the Professional level which does not include a source control product either.