Sorry, I was thinking that Paul had deleted the MDF to bring about a suspect state.

Sure enough, deleting a file doesn't work for me. The database comes up on...

jcrawf02 (6/24/2010)

---

Don't know if you guys are fans of Statistical Analysis, but there's a proposal for a StackOverflow model on stats, still waiting for enough folks to commit to make...

If possible, I'd also wrap any deletes in a transaction, along with a test to see if things work before you commit the transaction.

I know some people post that Diskkeeper (and similar tools) work fine with SQL Server, but I've always been nervous about anything accessing the SQL files while they're in use....

The compression is a CPU hit, but if you look at what happens with SQL Backup (Red Gate) or Litespeed (Quest), there is a CPU jump as well. SQL uses...

Is it the same time every day? Have you checked scheduled tasks in Windows?

If you can rebuild the clustered indexes, just do that. Indexdefrag should work as well. Here's a whitepaper that might help you decide which is better for you: http://technet.microsoft.com/en-us/library/cc966523.aspx

Congrats to all the candidates, and I think they're all worthy.

Here are some instructions.

http://www.sqlskills.com/BLOGS/PAUL/post/Disaster-recovery-101-backing-up-the-tail-of-the-log.aspx

Suspect mode is not necessarily corruption. You'd want to remove the a file and then startup the server to move it into suspect mode.

http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx

Why are you trying to force suspect mode?

Use the configuration manager to set the service account for all SQL Services. It will ensure the correct permissions.

I'm not sure that I completely understand you, given what you've written. Did you say that you added a data file to the database on an external drive and then...

You'll need to stop SQL 2000 or you can see some slowdowns. You'll also want to internally defrag the tables once the disk is done as things will have moved...

Quite fitting with today's editorial.