As I'm sure most people would tend to agree: why would you place your system files on C:\? In the event of issues from the OS-level or the drive...

You can omit this step " copy the temp files back from Z to the disk drive X"

When the SQL services is restarted, the tempdb files are recreated - there...

Just in case you were curious, all databases were restored successfully without losing any data - it took 14 hours to get them all back and to verify them with...

If you're just talking about where the actual data files are stored, this shouldn't be an issue. You can change SQL default data file location via the SSMS GUI....

Now I think I understand...

I see the datetimestamps are completely different...so it's basically reading it from the last known outcome of the prior CHECKDB that was successful.

I always thought it...

Yes, that's exactly the route that was chosen (even after explaining the consequences, and the possibilities of how much time/unknown data we could lose in the process).

Turns out that didn't...

I reset the status of the database in question and then placed it in emergency mode to run a checkdb with just error-msgs and got back thousands of errors (7MB...

The databases that are in suspect are on LUNS that came back just fine

So there is no other way? We are already restoring the DB that came from the lost lun

I'm assuming that the message "Check statement aborted. Database contains deferred transactions." means that SQL is still either rolling forward/rolling back transactions and I just need to wait?

My bad, no quotes as the parameter is of type sysname.

Click on the plus sing near the linked server (in the SSMS GUI)

Expand it, click catalogs...

If it throws an error...

Taken from a post elsewhere:

A new table or index is usually allocated it's first 8 pages from a mixed, rather than uniform extent. So, it's possible for each of the...

192K, still quite small. The effectiveness of an index seek on a table with so few little rows really won't show much of a performance hit/improvement that a table...

Don't forget the quotes...

EXEC MASTER.sys.sp_testlinkedserver 'ADSI'

I have also seen cases where uses are testing their procedures/queries and leave their session open...depending on the stuff they have been running, it can take up GB's in TempDB...