Before you start focusing on the server, I'd focus on the code and the structure of your database. Is the code set based or row-by-row? Is it using indexes to...

It's sample code from the BOL.

You could also set one of the parameters as OUTPUT and get it it that way.

ALTER PROCEDURE [Video].[addVideo]

@Title nvarchar(50),

...

13,000 or 30, if Access is going to require him to scroll through every select list to the bottom or it will retain a lock on that table... You have...

Straight out of the BOL:

USE AdventureWorks;

GO

-- Declare and set variable

-- to track number of retries

-- to attempt before exiting.

DECLARE @retry INT;

SET @retry = 5;

-- Keep attempting to update

-- table...

Jason Shadonix (4/17/2008)

---

Grant Fritchey (3/19/2008)

---

Hey, I lead a pack of Cub Scouts. I'm responsible for teaching them the "Fart Song."

[to the tune "The Yellow Rose of Texas"]

Oh, my body...

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...