1) You mentioned 300GB of local storage you might want to put tempdb on. It is CRITICALLY IMPORTANT to know what constitutes that 300GB "disk". It could be...

>> "you also have a pot-wad of indexes"

Jeff, is "pot-wad" a new technical term coined by the Standing Exceptional DBA?? 😎

patrickmcginnis59 (12/30/2011)

---

TheSQLGuru (12/30/2011)

---

I would try dropping off the PK from the table variable (note you do NOT have a temporary table here - it is a table var with many...

I would try dropping off the PK from the table variable (note you do NOT have a temporary table here - it is a table var with many things that...

Get a copy of the SQL Server MVP Deep Dives 2 book and read my chapter titled "Death by UDF" for some details on how devastatingly bad UDFs can be!!

1) I don't see where anyone asked this question so: WHY do you think you need/want partitioning at all? a few million rows per year is chump change unless...

Sorry, but I am at a loss here. You are now dropping columns off of the T3 query. This is too complex (for me anyway) to help you...

1) you still haven't provided what you think is the expected outcome for some set of rows that you think is giving you bad output.

2) your use of month-to-date is...

Dev (12/14/2011)

---

Ninja's_RGR'us (12/13/2011)

---

Go easy on the kid...

1) your last set of sample data seems to be missing the last 5 or 6 commas between the 'fields' of data.

2) you need to construct a SIMPLE set of...

Dev (12/13/2011)

---

Just a TYPO...

sp_who [ [ @loginame = ] 'login'...

Unintended cartesian product is likely culprit here. You need to catch it while it is running however. sp_whoisactive can show you the currently executing query plan and statements...

Some of the worst things I have ever had to clean up at clients came from the unfettered use of DTA. Use it (without sufficient knowledge and thought) at...

I will go with parameter sniffing too. BTW, next time you see this you do NOT have to bounce the box to clear it!! You can run this: ...

I have seen issues at clients where the prep/unprep stuff was a huge perf issue because it was getting called a bajillion times for stuff that was only executed ONCE!...