how sql objects manage with VSS?
can I Integrating SourceSafe / VSS with SQL Server 2005 ?
I want versioning sql schema?
A:
Please be more specific.
do you want to version control you schema?
or
do you want to use SQL server as your VSS backend?
Ali Shafai
2009-05-22 05:49:49
+1
A:
Aside from VSS being a total train wreck, if you want to store your schema in source control, one possible approach is to store the object creation script for each database object as a separate file in source control. That way, you can update individual parts of the schema easily. So you have a script for each table, trigger, index, procedure etc. As part of your build process these can be pulled together into a single script for ease of application to the target database.
ninesided
2009-05-22 06:19:24
Total train wreck: my experience as well.
rpetrich
2009-08-25 01:50:26
Although this approach works, it quickly becomes a maintenance hazard, as you need to keep up with the changes. Think of it as an additional task.
SoftwareGeek
2010-02-17 18:11:21
@Wisdom if you have some stringent QA processes in place, it doesn't need to be a hazard, but I'd love to hear of a better approach if you have one!
ninesided
2010-02-18 10:54:45
SoftwareGeek
2010-02-18 16:58:16
@Wisdom: I know exactly what you mean ;-)
ninesided
2010-02-18 17:48:47
@BhejaFry That's why you don't let developers make changes in a production environment - this can enforce all changes go through source control.
Rowland Shaw
2010-04-29 11:10:07
A:
Utilize tools like SQL Compare from Red Gate which will allow you to create schema, object per file, and then maintain the state of the files with VSS. I am currently trying to push that in my organization.
Roma
2010-04-15 15:55:46