What are the best options for putting SQL Server artifacts like triggers
into source code control, and then automating moving the objects from human
readable files back into the database as triggers?

Are any of the good options cheap?

We use VSS for source control of all DDL and code.  This is far from
"automated" and requires a good bit of discipline on the part of your
developers.  I've heard the following product is pretty good...
http://www.nobhillsoft.com/randolph.aspx .

HTH

MJKulangara
http://sqladventures.blogspot.com

Will (westes-usc@noemail.nospam) writes:
For cheap in terms of money, I can offer http://www.abaris.se/abaperls/
which is the toolset we use to load SQL object, build databases and
create change scripts. Not necessarily cheap in terms of labour hours,
we've been using this since 1996, and we constantly refining it, so it's
a bit complex by now. :-)

There are a couple of third-party tools out there, like DBGhost and
a few more that I don't remember the name of.

Hi

Along with the other suggestion you can always use EM or DMO to script into
individual files and then load them up. I suggest that you have specific
areas for different types of objects to avoid clutter.

John

Show quoteHide quote

Naming Conventions: Prefixing Columns w/ Table Names
Group By
column info from temp table
Oracle MINUS equivalent in MSSQL2000 ?
unique records