Hello Gail, I was going through the article. Its interestin topic as PKs and clustered indexes are the big factors for performance tuning.
I've a situation. I've one bg table A which is been used in one query having join with another big table B. Table A has no Primary key but a clustered index defined on four columns (composite) and two more nonclustered indexes. While running the query, its taking too much time and execution plan shows 23% of sort on one column of table A which is part of clustered index. How should I resolve it ?