Database Design

In my work experience several fields are put together to make up a primary key. Basically it is known that the combination of these fields will be unique. I have no problem with this if the combination of these fields (Primary Key) will be used as a way of accessing a row. However, it is known the primary key (Combination of Fields) will not be used to access a row. The fact of the matter is you plan to be able to select a single to multiple rows back using one of these two fields that make up the primary key, but never the two fields together (Primary Key). The Primary Key becomes purely academic with no practical use. Therefore, is this a bad database design?

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Thu Jun 15 2000 - 00:00:00 CDT