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.

Master, MSDB, and TempDB are defaulted to "Simple" recovery.  Master can be changed to Full Recovery and then I think you can do a transaction log backup.  Not 100% sure, though.

Thanks, Mark... it takes DOS-like wildcards (*) as well...

Have BCP do a Queryout from a sproc or a view that does a union between some column names and data... keep in mind that all of the data must...

Perhaps it's just a language barrier problem... but, if it's not, I agree with Serqiy... why would you need to count the number of columns present in a table?