Chris has the right idea with the Numbers table... except he didn't carry it far enough... we can do the whole table without a loop.

First, as Chris had in his...

Setting a database's Auto_Shrink property to ON is probably not the best idea in the world.  Something made it grow, you did something to reduce it's size, it's gonna grow...

By the way, if the definition of "set based" is...

- it opens the recordset (table in this case) once;

- it accesses each value in the recordset once;

- for any row...

Heh... hell no   According to some of the people I work with, you need to rebuild the power company

Heh... no such problems if you don't allow the coders to promote their own code and the DBA actually does his/her job...

Heh... you did that, too, huh?   

Dunno that, Tracey, but I'm still looking for the URL to the original article you sited...

Then we have some fairly quiet periods where we work on tuning things that don't work well.

Heh.. thought...

Then, have the batch precreate a file with the header names (using ECHO) and use OSQL to call the proc using the >> DOS append symbol instead of the -o parameter......

Care to share so we might all learn something?

Nice to see it when folks post both example data and code... nicely done, John.

... or, you can throw hardware at the problem ... r-i-g-h-t...

My recommendation in SQL Server 2000 would be to always drop the proc so that you can easily tell, just by the CreateDate, that you have the correct rev especially...

I recommend you don't post your password or server name anymore... just a thought

Yes... there's lot's of ways to do this... you can...

p.s.  Don't ever change the TempDB recovery mode... it's not necessary and will drop some performance.