EdVassie (8/10/2009)

---

MAXDOP 0 is often bad news. This allows SQL Server to produce a plan that does not take into account the resources on the box. I have...

Actually if it is an OLTP system the single most important thing to improve performance (part of which will come from reduced CXPACKET waits) is to have optimal indexing. ...

I have started giving my clients that very 'mandate' actually.

anish_ns (8/7/2009)

---

Were you originally tracing events like SP:StmtCompleted in the Stored Procedures category? Have you now changed to tracing events from the TSQL section like SQL:BatchCompleted?

I ask since you...

>>To be clear, I would primarily encourage you to patch your server with the latest fixes before putting more work into this - the problem you have may have already...

I can't...

1) Gail is right - use uniqueidentifier type for the GUID storage. 20-bytes per record savings there.

2) As another user pointed out, timespent is not only char based but...

Hopefully you have identified the problem as app-side (and you can do something to address it). Whether or not you have, I would still get the name of the...

IIRC there was also a bug where having a profiler filter on textdata that was longer than forty-some characters in length would cause a CPU race as well.

>> I assume that a parellelised plan will run the parts of the plan on one processor sequentially if there is only one not busy.

I don't think this is...

Using multiple CPUs will NOT speed up a query, and can actually make it run SLOWER, if your IO subsytem cannot supply data to the CPUs fast enough (which MANY...

Grant, aren't you supposed to be doing WORK at work?? 😀

I have spent a significant chunk of the last 2 years or so helping several clients refactor UDFs out of their databases due to extremely poor performance. It is...

Sanjays probably has the right solution here, assuming the number of rows matched is (or may be) low. Otherwise, you can force the plan to use a HASH join...

irobertson (7/30/2009)

---

Exactly 😀

Thankfully it's also a one off job, with a fixed data volume. The brief explicitly states "Performance is not an issue".

Until someone decides it isn't fast enough...