Mike,

May be you could place your database in the simple recovery mode before reindexing. Once reindexing is done you put it back in full recovery mode and do the full...

When we create clusters in our company they usually end with 'A' or 'B', depending on the Node..

So you can do something like that and include that in the job,...

It might sound strange, but did you perform a Diff backup of a physical Database...

If yes, then can it be a wrong ( with broken LSNs) Diff backup you are trying...

If you use Windows 2000 Server ( not Advanced Server, right?) then you cannot use the 3 GB switch

in the Boot.ini file with Windows 2000 Server; however, you can...

couple of points:

You made the original backup with SQL LiteSpeed, right?

We usually use extension LBK for LiteSpeed backups and are not using @with='RECOVERY' option for restore.

Also you might want to...

Shrinkfile/Shrinkdatabase might take quite some time on 300GB database...

Not sure if the following is true in your case, but: about 6 months ago I created few VB6/SQLDMO projects on my computer to run against our 250+...

you might want to run sp_who2  and store the output into the #table. Then query this table for that database usage and if necessary issue kill users...Then use your statement

I would assume that Auto close and Auto Shrink is off in Production

Did you check BOL?

check some of those links:

http://support.microsoft.com/kb/315886/

http://support.microsoft.com/?id=263556

http://msdn2.microsoft.com/en-us/library(d=robot)/ms189505.aspx

http://msdn2.microsoft.com/en-us/library(d=robot)/ms175189.aspx

forgot to mention: encorporate your code in the Stored Proc where the last line of code you can execute your xp_sendmail ...

in short: you can create a job where going to place above code and run it, say, every hour. If you do this on a regular basis you may...

are you running sp_who2 or sp_who2 active?

I heard from 2 different MS specialists a recommendation not to use Mirroring untill it will be fixed with SP1 available in June.

Is your TempDB has an adequate sizing?