Then there's THAT   Works almost everytime...

If you use OSQL with the -h-1 option and the -o option, something like the following works very well...

 USE Northwind

 SET NOCOUNT ON

 SELECT QUOTENAME('CustomerID','"')+','

      + QUOTENAME('CompanyName','"')+','

      +...

My pleasure... however, Wayne is correct... his method not only inherently checks the row counts, it also checks the actual data...

Ack!  A cursor?

Heh... understood and no worries... you've just got my curiosity up especially on the performance thing...

Sorry... missed the fact that you were still working on this to take variables... I'll take a crack at it over the weekend...

Sorry... didn't read the whole thread... I pretty much repeated what David McFarland already posted.

Agreed... BIGINT will certainly work... But consider a couple of things before you decide to use any numeric datatype for any "numbers" column such as credit card numbers, bank account numbers,...

Gosh, you would think so... I guess I understand why some folks don't, though... some DBA's don't practice what I consider to be the cardinal rule of being a DBA...

Once again, your ideas are extemely sound, but I see no code from you...

Start with OSQL -L

I agree with Aaron and Remi... there is no need for any dynamic SQL here.  Also, you must follow Aaron's suggestion for how to test for the presence of a...

Bond a DBA or whatever is necessary, but no matter what the circumstance, the DBA must be a trusted individual in order to protect the very security required by SOX......

First of all... INT is NOT capable of storing a 16 digit number so just forget about that.

Serqiy's idea is great but you must take that one step further... every...

And, to add to Seqiy's good questions, what does the table parameter look like?   Is it merely 2 dimensional or is it N dimensional?