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?

Nice gesture... but a really, really bad thing to do...

I think you mean that trailing spaces are neglected...

Spot on, Serqiy!

Documentation? ... ... Documentation??? ... ... DOCUMENTATION!!!!  Now THAT's what I'm talkin' 'bout!!!

Very nicely done, Alain!

Didn't know SAP made a version for SQL Server... that's cool.  Gotta look that one up.

Then you can write a stored procedure that figures all that out (provided CATEGORY is used in a normalized fashion) and DTS the results of the stored procedure or put them...

Yep... no database should ever be set to autogrow by 10% including TempDB... Estimate the maximum size you'll need for the next six months (or a year), add 20%, and...

Not entirely clear on what you want to do... do you have data in SQL Server that you want to spool out in a similar fashion?  In other words, where...

If you use Enterprise Manager to join many tables with outer joins, it will frequently produce both LEFT and RIGHT outer joins.  It will also, on occasion, produce joins that...

If all of this is happening in an explicitly declared transaction, that would be the source of your problems.