Looking at that data, I don't see anything running especially slowly. There are no blocked processes. Are you sure that the server...

Better than sp_who2, take a look at the DMV sys.dm_exec_requests. That will show you currently running queries. You can combine it with other DMV/DMF to arrive at the query being...

You can put a RAISERROR statement within the CATCH statement of your error handler so that, assuming the error needs to be returned, you can raise it and it will...

Use either TOP or MAX to get the value you want. Usually, depending on your indexes, TOP is the better approach. Just remember that TOP needs an ORDER BY statement....

john.imossi (9/1/2009)

---

I've had a go and got something like this:

DESCLARE @FromDate VARCHAR(20), @ToDate VARCHAR(20);

SELECT *

FROM Table

WHERE Date BETWEEN CONVERT(DateTime, @FromDate, 103)

AND CONVERT(DateTime, @ToDate, 103)

This runs but it returns no...

It's in the options under Transact SQL, Intellisense. If Intellisense is enabled you can turn on/off outlining.

Congratulations! I wish I could swing by.

Paul McCurdy (8/31/2009)

---

I see where using a version id vs Y/N indicator makes more sense, but am confused as to how the FK relationship would work. Let's say the region...

Without, at least, the execution plan, there's no way to understand what's happening on your end. What you're describing is not normal behavior. I'd love to understand what's causing it.

You really don't want to be changing primary key values. It's going to lead to all sorts of issues. A design I've used multiple times to track versions basically results...

That's almost 180 degrees away from what people usually complain about, how NVARCHAR slows things down because it's bigger than VARCHAR. Bob probably hit the answer with parameter sniffing. What's...

I agree with Steve. When you go in to have the conversation, one of the easiest ways to inform them of activity lulls is to capture user connections for...

Maybe not the greatest approach to the solution, but you could just add WITH MAXRECURSION = 365 query hint. Recursion is limited to ~32,000 calls.

We've got different thresholds for different servers. Personally, I'd say yours are too high if it's for an OLTP system. 60 seconds is a really long time (or should be)...

There are further error messages available. With only this, it's impossible to tell you what the problem is. It could be almost anything.