LOLROTF.

I need to put this up in my office .

Run out of bigint???

Any case scenario you can present?

Starting from 1, that's over 2 Billion rows inserted.  If you expect way more than that, then I'd suggest using bigint.

No it's very clear.  You just need to search these forums for hierarchies and you'll find plenty of solutions for sql 2000.  In 2005 the new solution is to use...

It is limited by the upper limit of the datatype used.  So the solution is to change the datatype, r even better, choose the correct one from the get go.

No offense Loner, but you really need to go out and Watch the movie "The Secret".

Just trust me on this one .

Open table and change the data.

I still think there's something fishy here but I didn't want to keep bothering him when he obviously had better things to do!

I think I'll just stick with my MAID... just to make things clear .

Lol, blinded by money... that might be a new song .

Hard to comment on that since we still don't know what problem you are trying to solve.  Since you seem to be somewhat new to SQL server, you might ask...

Then there's always option b : simply store that unique id and drop the 255 varchar columns from the view.  That way only one column will be duplicated... pretty much...

Let me put it in my words, but I'm still not sure I completly understand your question :

All columns listed in the select part of the view will be...

I guess it was not the first question on your mind .

What would be the point of that???

You would now have to do 2 joins instead of one.  There would be only loss in that scenario.

What problem are you trying to...

Thanks for the feedback.