Hi Bret,
You are 100% right about the duplicate key issue. It is a duplicate key issue rather than calling it as duplicate row issue. I am not quite sure on what dbAnalytics application is doing here. I was only told about the issue and I have already started scratching my head about its internal operations to better understand this issue.
I actually missed one point to mention. The status column was added only to track this duplicate records and delete them at a later point. They do not have any business significance on their own. Hence, even the Status column will be dropped along with the ID column.
Hence, we will be left with only Name, ClassName and GroupName columns. We are worried about the performance of creating a clustered or non clustered index on these three remaining columns at this point.
I hope it is clear now on what I am trying to achieve here. Please let me know if any additional information is required.
Regards
ADNAN