troubleshooting Question

What are the consequences of putting a NON CLUSTERED index on a PK column?

Avatar of sqlagent007
sqlagent007Flag for United States of America asked on
Microsoft SQL Server 2005
1 Comment1 Solution337 ViewsLast Modified:
I have a table that gets HUGE (250 MILLION records), the only thing that happens to this table is INSERT and SELECT.

Some of the searches by date appear to be slow, so we tossed around the idea of putting a NON CLUSTERED index on the data column. The date column is part of a composite key. RID+INSDATE is the primary key, so I know the insert date is already indexed.

Any suggestions why I should or should not?

Thanks!
ASKER CERTIFIED SOLUTION
tigin44

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 1 Comment.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 1 Comment.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros