For SQL 2000 and v7.0 this is true. In earlier versions you could but why would you ?

Here is the list Jeff mentioned early in the post (I may post more once I get through the thread:

Here's my 'short list' for tuning:

Round I

    DBCC UPDATEUSAGE

    UPDATE STATISTICS...

Start doing some homework first. On this site use the search feature for "tuning", "optimization", "performance", "join", "cursor". That ought to give you a pretty large start. Next visit

Our server standards are as follows:

Internal RAID 1 array (dual 36 Gb 15K rpm disks) with battery backed controller - 3 logical drives.

• C: for the OS, pagefile
• E: system logs, SQL errorlogs, SQL...

the actual error never made it into the post.

Not totally sure on 2K5 but on 2K I can answer. That depends on the method of execution. If you do all table REINDEXES followed by all table UPDATE STATS you...

Aside from the testing with the Cluster Administrator as outlines in Technet we ALWAYS perform the following tests after clustering and SQL Server is configured and installed:

• Both nodes up -...

I tend to agree with Doug on this one Steve. No power and inclement weather ... well missing one editorial or newsletter seems acceptable. Maybe you have even fallen victim...

Have you added  computername\IUSR_computername as a Windows Login to SQL Server ???

Just shut down SQL Reporting Services ... after this is complete then those databases can be treated just as 'user' databases'.

If you reindex do not forget the execute sp_recompile for the table(s) affected and sp_refreshview for the view(s) affected. otherwise you will have up to date statistics and stored procedure...

It still behaves the same because the databases already exist (they were created with the extra slash in th path). If you create new databases they will not have the...

You may also have to look at your NAS (Network attached storage) or other servers depending on where these devices actually map to. Potential causes other that local SQL Server...

here's a quick way to test and/or verify what the problem is:

declare @cmd varchar(64)

select @cmd='dir D:\BACKUP'

exec master..xp_cmdshell @cmd

If you can afford a couple of SQL restarts I'd first get the tempdb down to it's initial size on fresh installation - 2 Mb. Then I would immediately allocate...