Checkpoint will only return the 'command completed successfully' There's no more details than that.

You really don't want to run CLEARPROCCACHE & DBCC DROPCLEANBUFFERS on a production server, especially not on...

Yeah, but it's not going to throw a syntax error. Just won't do as he's expecting, which he probably didn't notice.

Yes, but i do think an UPDATE locks the table itself, not just the row being updated.

It depends. If you're updating the entire table, a table lock is very likely...

If you don't have a backup then fixing a corruption problem (if you do have one) will be unpleasant. Is this a production database?

Run the following. (replace <dbname> with the...

Actually, that nolock syntax does work.

Here's an odd idea, may help, may not. After the truncate, update the statistics of the table you've truncated. Truncate does not affect the rowmodcnt,...

Run a DBCC CheckDB on that database ASAP. It sounds like you may have some form of corruption in the db.

How long have you been getting that error? Got a...

It depends on the size of the table, the number of rows been updated, the indexes on the table, the amount of locks already held, and probably several other factors...

As mentioned, check AWE/PAE to ensure SQL can use over 2GB memory.

With 4GB memory, set the max server memory to aroung 3GB. Limiting the OS's memory to under 1...

#6DF65D3E is the type of object name given to a table variable. The most likely origin of that is the function dbo.splittext, which looks like a table-valued function.

It could...

If you're likely to get widely varying parameters, try marking the proc WITH RECOMPILE.

Alternativly, if some params are more common than others, you can try the OPTION (OPTIMISE FOR... hint...

Random thought - is you server 64 bit or 32? How much memory?

Then it's definatly a parameter sniffing issue. Can you try another .net experiment please?

First revert back to the old stored proc, without the variables.

This time, instead of passing the...

Can't see the images, because they're on your machine. Could you paste the differeing lines of the exec plan, as well as the query that you called the .net with?

Thanks

It could be parameter sniffing. I wouldn't think so if you used the proc in SSMS, but is a possibility.

Can you post the proc, the code you used to call...

Have a look at the exec plan for both, see what the differences are.

In management studio, just run with the execution plan option on. for the application run one, you...