Don't use ISQL.exe for any batch process... it is severely deprecated... use OSQL.exe instead.

I'm thinking somebody is going to need a comma or two in there

Please explain what you mean by "when it rolls over into the next range".  Also, it's been 2 months and you still haven't posted the exact error message.  Might also...

While this may sound incredibly simple, it is also incredibly common... have the network guy check the "duplex" on all the "boxes" in the connection chain to that remote server......

I think "business intelligence" is a bit of an oxy-moron when it comes to management... if you can't get them to invest in intelligent/skilled people to run and protect their...

Just my 2 cents... My testing shows that following all have identical execution plans and they all take an average of 1004 milliseconds to run...

DECLARE @BitBucket  INT

--===== WHERE...

Timeouts frequently have nothing to do with duration.... sometimes if tables are locked for update by a long running explicit transaction, you can get a timeout almost immediately.

Also, don't forget... that if you have any VARCHAR columns > 4000 characters, you could have a serious problem with truncation...

And please provide the query that allowed you to select which rows you want deleted!  Stop making us guess!

Nah... you can get INDEX SEEKS out of non-clustered indexes... they just won't be CLUSTERED INDEX SEEKS.  And, (as you know, ol' friend), I don't think they'll come close to...

You'll never do better than an INDEX SCAN with all the queries written so far... not sure there's one better, either.  Might be able to tweek a couple of things...

I don't remember where I got these from... they seem to work... of course, the spreadsheet must already exist but you can make a master template, copy it to a...

That'll definitely work although it doesn't do much for the amout of time it will take with all the indexes the orginal poster portrayed.  Not sure it'll do much for...

25,000 tables... 20-25 gig of default data... how big did they make TempDB in total (I realize you have it partitioned)?

Just one more question... why spreadsheets... why not print reports?