under your not EXISTS clause, are you sure all the join conditions cover the primary key on the main table?

I know that you are running InDepth, I don't know if you are gaining any real useful information out of it. I didn't want to spend the money to get...

The 100% cpu is definately related to SQL?

When you are hitting these cpu levels run a quick query to see what's going on, get an idea of what processes within...

Are you loading data from a remote server, or is it from locally held files?

The other thing is, did you install the OS from scratch yourself, or did you have...

If this is windows/sql 64 bit you don't need to add the switches as the 64 bit OS supports that memory natively (nicey nice, one huge reason for going to...

You also mentioned that the server is a 4 way xeon, but the xeon is a 32 bit processor, how can you be running 64bit SQL?

You state that the cpu levels are at 100%, is the task manager showing that it's SQL that using that cpu, or is there another process?

I used to get the error, used setspn and the errors went away. I use windows/sql auth and linkedservers.

You can prevent these errors by using the setspn utility from MS. This is available from http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/setspn-o.asp

Usage:

setspn MSSQLSvc/servername:1433 accountname

setspn MSSQLSvc/servername.domain:1433 accountname

where servername is the server, domain is the domain...

the WITH FAST option improves the speed of the showcontig as it doesn't bother checking certain objects, however, you will still get severe locking.

The best way is to schedule...

I second Phils notes with regards restores. Not had the corruption of the database, however trying to get a restore to work with those Agents is almost impossible.

I'd go out...

You can remove any services (ie sql server agent, full text search) from forcing a failover on service failure, so that's not so much of a problem.

You will only get the software related failover if the application built is cluster aware or runs on a service that you can manage through the cluster software.

As an example...

for a given database you could run sp_helpuser 'username'

to run for all databases

sp_msforeachdb "use ?; exec sp_helpuser 'username';"

More than likely someone is dropping an object and so EM is confirming whether or not the database is marked for replication (which would prevent it from being dropped)