An example that may work for you (as mark suggested in the link provided);WITH Dups AS (

SELECT

[Patient_Count]

,[Read_code7]

,[Read_code]

,[Current_Caseload_Holder]

,[Staff_number]

,[Event_date]

,[Event_done_at],

ROW_NUMBER() OVER (PARTITION BY [Read_code7],[Read_code],[Staff_number] ORDER BY [Read_code7]) AS Cnt

FROM MyTable

) SELECT * FROM...

Definitely sounds like an issue with the mapped drives (this happens) - don't suppose the external storage is a READYNAS or something similar?

While not sure it's the cause of your...

There is virtually no difference...

What (if anything) does your System/Application Event logs have to say?

Have you tried writing it locally first, then copying?

Not that this would be a solution, but it would prove there's an issue with the UNC mapping - issues with mapped...

Thanks for all the GREAT responses everyone. I had actually tweaked an existing index to get the query down to a few seconds, and at one point attempted the...

Was this link of any use to you?

BTW, I am using SQL 2008 EE, not 7,2000

Did you ever find an answer to this? I have a similar situation: I have a query that consistently showing 2.4 million reads in profiler, yet running the exact...

Yes it should be set to a fixed amount...and other equally important items are outlined quite plainly in the article I pointed out from idera (above) - have you had...

This is a good article outlining tempdb, it's not too lengthy and should help answer your questions:

http://www.idera.com/resourcecentral/whitepapers/demystify-tempdb-performance-and-management

It will definitely answer your questions regarding how to set the growth...

You could also check to see if there are any lingering/old/unused spids that can be killed - in our shop we have report writers that will run rather large queries...

So...just tweak what I already posted? Something like:D-ECLARE @OldTable TABLE( col1 varchar(1), col2 int, col3 int, col4 int, col5 int);

D-ECLARE @NewTable TABLE( col1 varchar(1), col2 int, col3 int);

INSERT @OldTable VALUES...

Assuming the NewTable has at least 1 column - in it's simplset form:

INSERT INTO NewTable

SELECT SUM(col1 + col2 + col3 + col4 + col5 + col6 + col7) FROM OtherTable

Test

D-ECLARE...

I am familiar with the wildcard operator and like everyone else, the answer should have been 2, but because of the insert issue, I also chose 0 knowing that the...