Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
tchinedu
Yak Posting Veteran
71 Posts |
 Posted - 2006-07-18 : 17:43:56
|
| Please help guys,We are trying to find a solution to the problem of tracking changes to SQL2005 server stored procedures and Table schema.What would be the best solution for tracking changes to sql schema and scripts etc.Please help |
|
|
timmy
Master Smack Fu Yak Hacker
1242 Posts |
Posted - 2006-07-18 : 18:45:34
|
| Apparently you can use DDL triggers to write audit logs to allow you to track changes (I'm a bit new to v2005...)But it would probably be easier to use another tool such as sourcesafe. Do a search on the forums for 'version control' because there's been lots of talk about it on this site.HTH,Tim |
 |
|
|
tchinedu
Yak Posting Veteran
71 Posts |
Posted - 2006-07-18 : 18:54:09
|
Thank you sir, That was my question exactly, is sourcesafe 2005 the best solution for tracking changes to sql2005 tables and stored procedures.....I'm looking for a solution that would best serve our needs, we need to be able to dynamically manage changes whenever we deliver new builds of our app and SQL table and script management has been a tough one...How do we go about doing this...In Source Safe, asumming it's the recommended solutionquote:
Originally posted by timmy
Apparently you can use DDL triggers to write audit logs to allow you to track changes (I'm a bit new to v2005...)But it would probably be easier to use another tool such as sourcesafe. Do a search on the forums for 'version control' because there's been lots of talk about it on this site.HTH,Tim
|
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-07-18 : 18:56:18
|
| Sourcesafe is one such tool to use, but there are many other source control software packages. We use Rational ClearCase here. I believe others use CVS. Most people would argue against using Sourcesafe, the 2005 version may be different though.Just use whatever source control package you are familiar with already or already own.Tara Kizer |
|
|
|
timmy
Master Smack Fu Yak Hacker
1242 Posts |
Posted - 2006-07-18 : 19:00:58
|
| There are a couple of packages out there to assist you building new versions based on the contents of CVS databases. RedGate do one, and one of the upcoming Visual Studio Team editions will be able to do this too. At our work we have a home-grown system that applies database changes based on VSS. I can't comment on the commercially available apps, but I would be interested to hear what others think of them.Cheers,Tim |
|
|
|
RayG
Starting Member
2 Posts |
Posted - 2006-07-24 : 17:29:37
|
| My 2 cents worth, treat the stuff as you would your code. We use VSS 2005 for Version Control of Database Objects (Although I also use ER/Studio to maintain the data model Also stored in VSS).We use DBGhost in development to keep individual developer databases up-to-date. Great in a dynamic development environment. Its an inexpensive yet very powerful solution.Even our build process use DBGhost Automation components to apply the Delta to the previous version DBs. Paired with DB level Unit tests we get to know if there is a problem everytime the build is run.I am currently working out how to migrate production DBs with DBGhost as it is much more thourough and flexible than I would ever be for keeping 60+ DBs current.If anybody else out there is a DBGhost fan and wants to do a knowlege exchange please e-mail me: canada.com rgagne@ |
|
|
|
|
|
|
|
|
Tracking Changes to SQL 2005 db