Yep... know that... see my post above...

Heh... dunno... must be a new "feature" than MS built in... 😉

Heh... yeah... it's a shame that MS can't figure out the best of both worlds. Having just seen 2k5 for the first time and the apparent mess they made...

Heh... from where I sit, most of them never did, so no real change. 😉

Actually, it's a common problem... take a look at what you have for a "default catalog" when you login... credits to Navy beans says it's "Master".

Thanks, Matt... I was afraid you were going to say that... yet another highly useful tool shot into the bit-bucket by the idiots that designed the interface for 2k5. ...

Heh... that's a bit selfish and we're not your personal consultants... if an answer is determined, it should be posted here for all to see.

There're...

Any code that needs the word DISTINCT in it, should be highly suspect as the source of a lot of reads... hidden RBAR...

Just trying to make sure...

1. Are the 2/3 detail rows in a different table than the "combined" table?

2. If so, are there rows already in the "combined" table...

SELECT * FROM INFORMATION_SCHEMA.PARAMETERS WHERE Specific_Name = 'Award_Category_Insert'

Um... why not just replace all INT with BIGINT in the table declaration? After all, you're already violating the 8060 rule for row size... what's a little more going...

What should you use instead?

Or, use BCP with the -m (Max errors) parameter set to some ridiculously high number and the -e (err_file) set to a file name in the same directory. This...

Um... be careful... ISDATE() lies almost as bad as ISNUMERIC() is when you try to use it as an ISALLDIGITS function. Sure, the following will allow a conversion, but...

So why do you recommend creating the table first?