GilaMonster (12/26/2013)

---

kapil_kk (12/24/2013)

---

GilaMonster (12/24/2013)

---

kapil_kk (12/24/2013)

---

Should I drop unique constraint and make non clustered index only or add more column in unique constraint instead of creating another nonclustered index?

If the index is there to enforce uniqueness, then it needs to be there, as-is to enforce uniqueness. Otherwise you're reducing the integrity of the database by potentially allowing duplicates.

Have you done performance tests? Is the performance of queries using this table inadequate?

Yes, uniqueness are required.....

Then you can't add more columns to the unique constraint

While running my stored procedure I see bookmark lookup so I thought to avoid that if I add my non clustered index columns to the unique non clustered only... due to that index also get reduced

So there are key lookups. Are they a problem? Is the query not meeting it's performance requirements?