Not the solution, but the reason.

When rebuilding an index, the old index is only dropped once the new one is complete. It's for ease of rollback (can just drop the...

Stock standard copyright...

Yup, or set up an extended events session to run permanently. Dunno if the latter would meet your requirements though.

Unless you have some custom logging implemented, you can't get that info. SQL doesn't track it.

You're going to have to give us a lot more info than that to help you debug.

A backup is the size of the data in the file + the amount of log space needed to restore consistently. It is not the sum of the sizes of...

As with most things, heavy is relative to your app, not an overall distinction.

Look in Books Online for the definitions of the fields, google for any articles or blog posts...

You want me to go to google, search for statistics, then link some of the articles that google finds?

Kill the query so that the user gets annoyed and re-runs it?

If you're running out of space for TempDB you need to either change the queries so that they...

Can't be done. If the client wants point in...

A restore has to create an entire database, hence mdf and ldf. The log file is not an optional part of the database.

There are tonnes of blog posts and articles on statistics available. Spend some time with your favourite search engine and you'll find lots.

That's not contention, that's just queries using a lot of TempDB.

Query the sys.dm_db_session_space_usage to identify sessions using lots of TempDB. You can join it back to sys.dm_exec_sessions to get the...

Define 'TempDB issue'? Why do you think it's TempDB contention?

A restore recreates the database exactly as it was when it was backed up. The only thing that puts a checksum on a page is when that page is read...