There is a new way to implement version control in SQL server: It's a
new tool out there, and right now, since their latest version is out in
beta, its FREE!!
this tool is simple and does exactly what most developers\DBAs are
looking for: it simply scans your database in the background for any
changes, and if any found, it will save them in its own internal db and
also push it automatically into SourceSafe. What you get, without any
action on your part, is all your DB entities already in SourceSafe (or
in the software's internal DB, if you dont want it pushed automatically
to SS) with a full log of what changes took place and when. that's what
it focuses on, and that's what its good at. it has some other useful
features (grep TSQL code for some subtext, code comparison, etc...) but
its not a query analyzer (or any other devlopment environment)
substitute. It doesn't demand any change in your regular work pattern.
You work with whatever tools you want, and rest assured that the full
version history is there. Heaven, isn't it?
new tool out there, and right now, since their latest version is out in
beta, its FREE!!
this tool is simple and does exactly what most developers\DBAs are
looking for: it simply scans your database in the background for any
changes, and if any found, it will save them in its own internal db and
also push it automatically into SourceSafe. What you get, without any
action on your part, is all your DB entities already in SourceSafe (or
in the software's internal DB, if you dont want it pushed automatically
to SS) with a full log of what changes took place and when. that's what
it focuses on, and that's what its good at. it has some other useful
features (grep TSQL code for some subtext, code comparison, etc...) but
its not a query analyzer (or any other devlopment environment)
substitute. It doesn't demand any change in your regular work pattern.
You work with whatever tools you want, and rest assured that the full
version history is there. Heaven, isn't it?