They are Cl index on small tables:

DBCC SHOWCONTIG scanning 'tblTag' table...

Table: 'tblTag' (1110295010); index ID: 1, database ID: 12

TABLE level scan performed.

- Pages Scanned................................: 6

- Extents Scanned..............................: 6

- Extent Switches..............................:...

we run a job from the monitoring server ( every 2 hours) checking if perfmon counters are running on the production cluster

you may want to run some scripts ( job) notifying you that when cluster failover occur and perfmon stop, you may want to restart them...

use DBCC SHRINKFILE instead of SHRINKDATABASE

make sure to flip your database in simple recovery mode while doing reindexing...

make sure to delete old tempdb files in original location after restart

use server side traces ( try to collect only needed info though) instead of profiler and you will be fine...

Maintain a central server (database) with all server names and make all servers as linked servers and run all your stored procs in the loop ( server by server) locally\OPENQUERY. Make...

Shoot in a dark: It can be your sysservers table in messed up?!

Also by placing select @@servername in a job and running it, say, every 5 minutes ( detecting...

1 TB was shrinkdatabasing for over a day, when I had to cancel it. 100 gb file was shrinkfiling for about 10 hours. However we got data back in 3 months....

If you have SS2K and SS2005 on the same box as well as VB6 and Visual Studion, DMO wouldn't work. Period. So I had to spent a bunch of time...

can't you just incorporate it ( using server server side trace) into Stored proc with sp_procoption?

Thanks guys, Anyone has a supporting link???

Colin, Most likely we will go for dual core, once we fnalize our budget.

After you enabled AWE, did you restart the box?

Can you do that in Stored Proc, so it will return zero records?