Jim,
>
>Show me an example of a table design without a primary key? I have seen some and it is always in a review of a system that isn't working correctly because there is no unique identifier of a record. Are you confusing the primary index with the primary key here?

I've got a program running, with a historical sales table:
Invoiceno, Articleno, Count, price, etc..

There is a possibility (don't ask for the circumstances) where there are wo the same articles lines on the same invoice. Since this historical table is only used for OLAP purposes and don't need to adress the records seprately, I don't have the for a primary key (since I won't be used anywhere in the system).

Though I agree, this table SHOULD have a primary key because someday you might have the need to adress them seperately, Yes there are circumstance where omiting a PK won't lead to drast problems. Remember the problems with using PK's in historical tables within the former thread.

Walter,