In the SQL server realm, the PK is typically a clustered, non-duplicate and autonumbering/seed identity column.
I typically apply non-clustered indexes for FKs. If the primary key is several columns, it will index better if the combination of teh columns is unique and thus you can create a clustered index on it. Teddy On 2/19/07, stylo stylo <[EMAIL PROTECTED]> wrote: > > > When I look in the administrator it shows an index on the id columns > > already if I'm reading it correctly. (in a box at the bottom right on > > the edit table dialog) > > > I see I misunderstood it. I was looking at the column index area bottom > right, not the indices on the left. So the converter has already added the > indexes that were in Access. > > Questions: > > Do primary keys need to be added as indexes even though they already show > as "primary key" in the table's list of indices? For example, I see the > products table has "primary" which is product_id, and also a "product_id" > index on product_id. Do I delete the 2nd one as redundant, or it is needed? > > Does the index name matter for any reason? I noticed they are all the name > of the column they index but one is different for some reason, just > wondering why. > > When would you add more than one column to an index? > > Thanks. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http://www.adobe.com/products/coldfusion/flex2/ Archive: http://www.houseoffusion.com/groups/SQL/message.cfm/messageid:2736 Subscription: http://www.houseoffusion.com/groups/SQL/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.6
