Thanks for the feedback, James.

Now there's an idea... thanks for pitching in...   hadn't thought about that approach.

If the first column is unquoted data, then the first column BCP would actually import a column (instead of "0" as the target column #) and you would, of course,...

Haven't tried it in Enterprise Manager... works fine in Query Analyzer...

Yep, I agree with Kory...

Also, I believe that moving the reference to constants out of the ON clauses and into a WHERE clause will help a bit...

The other thing may...

Hilight the character, copy it, and paste it into the 'X' below in QUERY ANALYZER... it'll tell you what the character number is...

SELECT ASCII('X')

Or...

SELECT REPLACE(STR(3,2),' ','0')

He did say that is was for fun and it does work for what James posted as a very limited original format

Yep, I agree...  if you need to fumble with fill factors for all tables, then you are correct... hopefully, though, you let the default fill...

No.  It wouldn't work for upgrades because the whole database is changed... and that brings up another point... if your "harmless, transparent upgrade" fails for some reason, where does that...

I knew it!  I've always hated composite name columns... I'm trying to get them to change it but we have a 3rd party app at work where they allow up...

What do I lookup to figure out how to change how the formatting is done?  All I could find was the following and it wasn't very helpful...

Format SQL

You...

If you have a pot-wad of data, I suggest you create a sister table with a UNIQUE IGNORE DUPLICATES key on it... copy the data to the new table and...

The names and ID's of the objects are stored in the SYSOBJECTS table.  The SQL for each is stored in SYSCOMMENTS and the ID in SYSCOMMENTS matches the ID in...

Yes, it would be faster to use a single file... but, then you'd also loose the granularity you need to check the creation of each stored procedure for errors...

I'm not...