Clustered Primary Key issues

[LARiot]

What problems other than performance can come about from using a clustered primary key? There will be no foreign keys referencing it.

In case you're wondering, a clustered key is key made up of more than one field/column.

Thanks.

 

[dhookom]

I have always used "Clustered Index" to mean an index on SQL Server that stores records in the same order as the index. From SQL Server Books On Line

In a clustered index, the physical order of the rows in the table is the same as the logical (indexed) order of the index key values.

However, performance should not be an issue with a multiple field primary key.

Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]

 

[PHV]

Are you sure you don't confuse cluster and composite ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[BNPMike]

I can't think of any problems from using multi-key indexes.

 

[Lilliabeth]

It seems every time I have ever used a composite PK (except just for junction tables), I ended up sorry later. Is it that it complicates combo boxes on forms? It's hard to remember because where I work now we are not allowed to use them at all.

Lilliabeth
-Why use a big word when a diminutive one will do?-