Seriously, stop wasting time on this script. It's been done, extremely well done already.

http://sqlfool.com/2010/04/index-defrag-script-v4-0/

2nd link in google.

http://msdn.microsoft.com/en-us/library/ms177463.aspx

Let me translate.

Jeff wants you to learn to do it yourself and he gave you the exact reference you need.

Plan B would be to use google for a fully made...

Actually this thread might segway well into the sort issue to find out how hard it's hitting the server.

http://www.sqlservercentral.com/Forums/Topic1090063-391-1.aspx#bm1090123

Above removing the order by and checking the disks.

Have you tried inserting intermediate results (for each join) to temp table? >> divide and conquer.

That would also tell you what join...

Called in for help... they shoud be getting here soon.

Good luck.

VLDB, very long query, out of my league :

http://www.sqlservercentral.com/Forums/Topic1090539-391-1.aspx

The most I can do from this point forward is send you this link.

This kind of problem is not my cup of tea.

http://download.microsoft.com/download/4/7/a/47a548b9-249e-484c-abd7-29f31282b04d/Performance_Tuning_Waits_Queues.doc

Ok, let's call in Paul Randal's magic "where does it hurt" button :

Run this and post back the results :

WITH Waits AS

(SELECT

...

What happens if you have a super fast disk array with 1 bad apple in the bunch?

Whereever you'll get the job for you to be happy.

Why are you using maxdop 1? Other than divide and conquer, I don't have much else to offer (a but outside my normal tuning table sizes).

How many GBs of data arer you exporting to disk?

Are you reading and writing on the same HD?

The most reads I ever got is around 1B and it crashed the server. So unless you're talking about a TB db+ then yes you may have a...

Well 12 months experience as dev is far from nothing... and recruiters will know that. You don't have anything to worry about.