that is not Quest's fault, it will most likely be down to slow proc. or I/O problems (you did say they are dev boxes).

I don't think there is much difference between SQL 2000 and 2005 with respect to using Quest/SQLBackup etc. They just use the VDI and pretend to be a tape system and consume data much faster than a tape could.

Would be interesting to see if there is much difference if you move your dev boxes to 2005.

that is not Quest's fault, it will most likely be down to slow proc. or I/O problems (you did say they are dev boxes).

I don't think there is much difference between SQL 2000 and 2005 with respect to using Quest/SQLBackup etc. They just use the VDI and pretend to be a tape system and consume data much faster than a tape could.

Would be interesting to see if there is much difference if you move your dev boxes to 2005.

Whooomph.

Way to miss the point.

A 1.5TB database takes a long time to restore. Especially on a low spec box.

The point about 2005/8 as GerbilDBA mentioned is that it gives us the snapshot option.

I was only making it clear to anyone reading the rest of the thread that SQLBackup or Quest are not the bad guys when it comes to a slow restore. Of course 1.5 TB will take a while to restore, but the two tools will restore this volume quicker than a native restore.

It is also quite important to remember that Database Snapshots are dependant on Enterprise Edition or Developer Edition, as I mentioned in a previous post, whereas 3rd Party tools can help for the other editions.

P.S. I am the original poster that suggested the use of database snapshots. I just changed my username on the forums from GermanDBA to WilliamD a few days after posting to this topic. My quoted responses remain with the title GermanDBA though.

AnyDbTest is one outstanding DB unit testing and data validating tool.(Official website, http://www.anydbtest.com).Writing unit and component tests for objects with external dependencies, such as databases or other objects, can prove arduous, as those dependencies may hinder isolation. Ultimately, effective white-box tests isolate an object by controlling outside dependencies, so as to manipulate its state or associated behavior.

If you are an app developer, you can utilize mock objects or stubs to for controlling outside database dependency. But if you are a DB developer, these mock and stub frameworks cannot give you any helps.

AnyDbTest provides an elegant solution for controlling a database dependency within applications by allowing developers to manage the state of a database throughout a test. With AnyDbTest, a database can be seeded with a desired data set before a test; moreover, at the completion of the test, the database can be placed back into its pre-test state.

Automated tests are a critical facet of most successful software projects. AnyDbTest allows developers to create test cases that control the state of a database during their life cycles; consequently, those test cases are easily automatic, as they do not require manual intervention between tests; nor do they entail manual interpretation of results.