Be careful not to confuse CLUSTERED with CLUSTERING. They are similar but slightly different. I'd have to look up the difference (of those definitions) before answering your question. I believe each table can have only one of those two, but cannot remember which. The one I am thinking of is how the the rows will be physically sequenced. hth
On Tue, 28 Dec 2010 23:58:09 -0500, Michael Dinowitz wrote > Fast question for those home on a snowed in night. Lets say I have a > table which has a primary key that is composed of 3 id fields. This > PK index is not set to clustered. I wanted to set another index that > contains one of the IDs from the PK but set to clustered. Is this a > good idea or will I have conflicts? > > Primary Keys (unique, non-clustered) > jointypeid > jointablekeyid > keywordid > > Want to index as clustered > jointypeID > > Just want to make sure that one index will not 'step on the toes' of > another. > > Thanks > > -- > Michael Dinowitz > Lead Author - Adobe Coldfusion Anthology > http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael- Dinowitz/dp/1430272155/?tag=houseoffusion > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/sql/message.cfm/messageid:3377 Subscription: http://www.houseoffusion.com/groups/sql/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/sql/unsubscribe.cfm
