I was not going to respond to this, but I can't help it. You just broadcast to the most helpful bunch of people in the world that you'll lie to...

Yes, please do what Micheal said. Use the OUTPUT statement to gather that information. Don't try to write logic to go back & capture it after the fact. When you...

No doubt you're seeing contention for memory & processor. You'll need to run Perfmon and collect counters on wait times to see what is waiting on what. Where possible (and...

Huh, I'd assume a try catch even on a single row single table update. Even there you could run into deadlocks, whatever, that you want to handle within the TSQL...

And how much do you want to bet that they don't have a tested backup in place either... I wish I didn't hate travel so much. I can see why...

OOPS! The "correct" answer generates an error.

Holy crap! That is some seriously heinous code. Makes you wonder what the database looks like doesn't it?

:sick:

If the query is really long and it's creating and loading huge temporary tables, it won't complete the transaction and clear the log of those temporary tables until the context...

The problem is, executing a dynamic query like that is creating a different execution context. As soon as that context clears, which happens when the execution finishes, the temporary table...

Also, for what its worth, you're doing unecessary work, selecting into the temporary table and then selecting from the temporary table. Instead, just use the select statement that would load...

Suspended means waiting. Something interrupted the process and it's in a wait state. I'm not that familiar with Access, but from what you're describing, Access is in some manner holding...

Either way you go, to ensure that you're getting the exact same result set you need to use ORDER BY to ensure that the 1000 rows you get is the...

Everything Gail said and look at your execution plan (I'm getting sick of typing that. Anyone have a macro?) to see which indexes have a positive affect and which have...

This looks like a fun one to pile on to

1) A bit field, all by its lonesome, can be a horrible choice for an index (although in rare circumstances as...

Some like this would work. Instead of just the SELECT statement, use that statement with an INSERT statement into the auditing table of choice.

DECLARE @SqlString NVARCHAR(MAX)

DECLARE @DbName NVARCHAR(MAX)

DECLARE MyDatabases CURSOR...