last_batch in sysprocesses is the place to look. Try an experiment yourself. Open up a QA session and run sp_who. Then let it go idle for 15-20 minutes. Then open...

For large operations (them 'batch') I'd opt for SQLCMD.

The sqlcmd utility allows you to enter Transact-SQL statements, system procedures, and script files at the command prompt. This utility uses OLE...

I disagreee. It can and should be in order to tighten security. However never do this without researching and testing. As far as I know the only reason that you should...

I too chose the closest answer (a reasonable guesstimate) but as always ran the T-SQL code just to make sure (especially since I could not remember that part of my...

I agree with many points ... most importantly, licensing is a nightmare and you need a reasonabley versed techie to use the sight. However this is one of the few times...

For such a short article it's certainly a lot to wrap your mind around !

We drop them from all environments.

... doesn't it seem counter productive to have an index where a portion of it may be 'NULL' ???

I'd try it again and in another window execute sp_who to look for blocking. Then maybe check the SQL Server errorlog and the Windows Event logs. As a last resort...

Before looking at the OS and configuration I'd start with:

Round I

    DBCC UPDATEUSAGE

    UPDATE STATISTICS (with FULL scan) for all tables

    exec sp_recompile for all tables

    exec sp_refreshview for all...

SETUSER is included for backward compatbility in SQL 2K5. BOL states you should use ECECUTE AS instead.

I can spot only a couple of differences between your process and mine. I use the Service Control Manager to start/stop things as a service during master database recovery. The other...

I just reread the entire thread. The 'error' you are getting after the master database has been restored is normal. Anytime the master database has been restored SQL Server immediately...

An absolutely wonderful article David. All to often it is sad and very true. I've had my share of blank stares out windows and walking the hallways muttering ... damn,...

Here's everything you need to know for SQL 2000:

http://support.microsoft.com/default.aspx?kbid=314546#top

http://support.microsoft.com/default.aspx?kbid=246133

http://support.microsoft.com/default.aspx?scid=kb;en-us;253817

http://support.microsoft.com/default.aspx?scid=kb;EN-US;240867

http://support.microsoft.com/kb/224071/en-us

http://support.microsoft.com/kb/304692/EN-US/

Have fun !