Please don't cross-post...

Actually, there's a lot that will trip up ISNUMERIC... please see the following URL...

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=243646&p=2

So... if you want an ISALLDIGITs and still allow conversion to the MONEY data type when...

heh... I guess I'm just gonna have to break down and upgrade one of these near days...

Not sure where to look, Koji... it's mostly personal experience.  Like I said, it's really half a cross-join... I guess my suggestion would to be to readup on cross-joins and...

Um.... they don't want it in T-SQL... they want an expression in SSIS and they said IsNumeric Doesn't work there...

Nope... not kidding.  THAT level of intelligence or training was, apparently, missing.  And, it's really hard for me to think that maybe I didn't ask the question correctly because I drew...

Yes... computer science is dead even if you have a degree in it (not you personnally, just a general observation). 

I've interviewed many a person that have Masters degrees in...

Dont worry... it's not a trivial question...

There's a half dozen or more ways to do such a thing... Koji posted one of them... but, beware... Koji's code relies on...

Very cool... thanks for taking the time, ALZDBA!

Not a problem... didn't take it offensively but I appreciate your feedback.  I still wouldn't mind finding out what the performance of your dupecheck is on SQL Server 2005 because...

David,

Peter is correct about a potential problem with my code and, I'm sorry to say, I completely forgot about it because of the way I load data for dupe checks.  If...

Ooooh... Sorry Peter... didn't mean to make that sound as a challenge... seriously, I've not had the opportunity to work with SQL Server 2005 and the method you used truly...

I see no reason why "the database design will need multiple instances of the single table".  I assume they mean "multiple physical copies"?  Can that person give an example of what...

My first question would be... what have you tried?

This smacks of the Oracle-like "sequence" number... the others are correct... why aren't you using the auto-numbering capabilities of an IDENTITY column?

Now, I'll also admit that there are requirements like...