Re: Does it make sense to have 2 unique keys in one table?

dmajor7@aol.com "Dmajor7" writes: : Although I am no expert in this area, it seems to me : that you could gain some performance by not requiring key1 to be unique. : Key2 being unique is going to insure that key1 is unique anyway so why : waste time having the database check for something that is impossible. If I had a penny for every row of bad data I had to clean up because the programmer thought that was "impossible" I'd be rubbing elbows with Bill Gates! :) As a data administrator, I want the engine to enforce every possible check, especially on things that are impossible--to be *sure* that they are impossible. Even then companies like Verity and Vality are making a killing cleaning up databases. OTOH, as an applications analyst I'm concerned with the engine taking up extra time, and it would eventually be possible to load an application with so many checks and balances that it wouldn't even run. The bottom line is: if your data is worth having, it's worth having right. Take the extra time and have the database check it. __________________________________________________________________ | Clem Akins Standard Disclaimers Apply | |Reynolds Metals Co, Alloys Plant "Climb High, Cave Deep!" | | Muscle Shoals, Alabama USA cwakins@leia.alloys.rmc.com | |________________________________________________________________|