Database Change Management
Database Change Management
Home | Profile | Register | Active Topics | Active Polls | Members | Private Messages | Search | FAQ
Save Password
Forgot your Password?

 All Forums
 Managing Changes To SQL Server Code
 General SQL Change Management Discussions Forum
 Upgrading database files on a file system
 New Topic  New Poll New Poll
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  


1 Posts

Posted - 12/02/2006 :  17:44:55  Show Profile  Send ricalves74 a Yahoo! Message Send ricalves74 a Private Message  Reply with Quote

At my company, we currently have a “home grown” tool, WUT (Wholesale Upgrade tool), that propagates database changes from a SourceSafe location to over 1000 SQL2000 database files (SQL back up files) on a file system.

In case you are wondering why we are doing this... These databases are used for automated testing purposes. We currently have many parallel development efforts that this tool is used very frequently.

WUT scans a “DB Tree”, restores a database, executes upgrade scripts and performs a backup of the database back to the file system. The automated tests will then restore this database and perform a series of functional tests.

We are currently looking for a supported solution that will replace this tool. The build group does not like the idea we connect to SourceSafe so we need to look for alternative methods, such as using a file server after the build process ocurrs.

Are your tool sets / products able to automate these database upgrades/changes in this manner?



Ric Alves

Edited by - ricalves74 on 12/03/2006 11:28:30

Google AdSense

Mountain View


125 Posts

Posted - 12/19/2006 :  02:55:41  Show Profile  Click to see leachm's MSN Messenger address Send leachm a Private Message  Reply with Quote
Hi Ric,

I have seen DB Ghost used in such an environment, however, there were only 45 different test environment not 1000!

the good news is that the process DB Ghost was used in scales very well. The steps would be:

1. Restore a copy of the target databases
2. Build a new database from the object CREATE scripts in VSS using DB Ghost
3. Compare and upgrade the target database using DB Ghost.
4. Back it up
5. Restore it on the target SQL Server machine

Would this process work in your environment?

Also, could you give me some more detail about why your build team don't like you connecting to SourceSafe?

Lastly, once you have upgraded all 1000 databases do you expect their schemas to be identical? If so then the above process could simply be executed once to create the latest, greatest schema version and that could be restored to all 1000 target environments. When the automated test scripts ran they could simply insert all the test data they need as the first step in the automated test script.


Malcolm Leach
You must be logged in to see this link.
DB Ghost Build, Compare and Synchronize = Change Management for SQL Server

Edited by - leachm on 12/19/2006 03:00:59
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  New Poll New Poll
 Reply to Topic
 Printer Friendly
Jump To:
Database Change Management © Copyright 2005 Innovartis Ltd. Go To Top Of Page
Snitz Forums 2000
RSS Feed 1 RSS Feed 2
Powered by ForumCo 2000-2008
TOS - AUP - URA - Privacy Policy
ForumCo Free Blogs and Galleries
Signup for a free forum or Go Banner Free