Prayer and living sacrifices to the gods...

Barring that... It's not that bad. It could be worse. It could be SQL Server 6.5.

Standard stuff. Make sure you have backups in place....

Brandie Tarvin (10/7/2010)

---

jcrawf02 (10/7/2010)

---

it's that whole theory about how time-travel is impossible because once it's possible, you'll inevitably change things in such a way that the timestream it was...

Gianluca Sartori (10/7/2010)

---

hahnorlaska (10/7/2010)

---

The attached show plan statistics outputs gives detailed information on what was being done to process the query (the physical operator. logical operator, argument, objects involved (indexes),...

Alex-815008 (10/7/2010)

---

Thanks for the explanation, I think I see what you're saying.

I'm surprised there is such a limitation because I thought that actually it was common for there to be...

Alex-815008 (10/7/2010)

---

Still not seeing it :unsure:

I've searched that article for "resolution" since that seemed to be a key part of what you were saying, but I only found references to...

vijay1327-891581 (10/7/2010)

---

Thanks for the quick reply.

But the problem is the company does NOT allow to run the profiler due to some policies. hence I was trying to find if ther...

Alex-815008 (10/7/2010)

---

Which link in that reference should I follow...

I'd look at the other wait states and queues on the system. You know you're getting lots of disk i/o's, but why? You need to figure out what is causing...

Without the execution plan it's just guess work to what's going on. Remember, just because you see an index referred to in the execution plan doesn't mean it's being used...

Basically, I'd rely on perfmon for those metrics. It's should be gathering what you need.

The real question is, what are you trying to figure out? What's happening on the...

Regularly running at 50-80ms for page life isn't good. I'd look to see if you're getting good plan reuse, are you getting lots of recompiles? I'd also take a look...

Because one of those errors is dependent on resolution of action, it's not caught by the TRY/CATCH. It's explained here.

That's a server level query. The security setting on it is View Server State, not View Database State. So it includes the DB_ID so that you can filter for a...

barry.smallman (10/7/2010)

---

Hi,

Yes, I tried amending the SP to query the sys.dm_exec_connections DMV as suggested in the reply by Lowell!!

When the stored procedure failed to run this morning, I started investigating...

CirquedeSQLeil (10/6/2010)

---

Grant Fritchey (10/6/2010)

---

Alvin Ramard (10/6/2010)

---

Grant Fritchey (10/6/2010)

---

See what I miss by trying to have a life & stuff. Gotta stop doing things away from...