> Thanks for you answer, I mistyped and said 25 instead of 15 ....
Anyway this was my opinion also but the customer wouldn't believe me and
immediately pointed to Oracla, which is capable of doing this without any
problems.
thanks again for the confirmation,
It's possible to do a lot of stuff with software that is not advisable. If
you client has no actual application that needs that many columns in a
unique index, and they are just comparing "numbers" in order to choose a
DBMS product, you should point out to them that having even 16 columns in a
unique key is very poor design, and having that limitation is a blessing in
disguise to prevent a poor design from being implemented. You should also
point out that as the index gets larger, performance suffers (not to mention
having to process that many columns in the WHERE clause of an SQL statement.
So the 16 column limitation is a safety feature (not a limitation) to
prevent bad design being implemented that Oracle does not have.