Non-Cluster Index Primary Key

I inherited a SQL Server 2000 database that has performance issues. I
noticed the primary keys are set up as non-cluster indexes.
By default the table primary key is created as cluster indexes. Could this
cause a database performance problems if these are large tables and access
often.
If the table were set up with the primary key as a non-cluster index?
Thanks,
There is no requirement that the PK (or any index for that matter) be
clustered. But it is recommended that every table have a clustered index.
Which one depends on how you are using it. You have to narrow down the
performance issues much more before anyone can answer this question. See if
these help:
http://www.microsoft.com/sql/techinf...perftuning.asp
Performance WP's
http://www.swynk.com/friends/vandenberg/perfmonitor.asp Perfmon counters
http://www.sql-server-performance.co...ance_audit.asp
Hardware Performance CheckList
http://www.sql-server-performance.co...mance_tips.asp
SQL 2000 Performance tuning tips
http://www.support.microsoft.com/?id=q224587 Troubleshooting App
Performance
http://msdn.microsoft.com/library/de...rfmon_24u1.asp
Disk Monitoring
Andrew J. Kelly SQL MVP
"Joe K." <JoeK@.discussions.microsoft.com> wrote in message
news:17DC89CC-A77A-486E-BADF-60AC39B5A973@.microsoft.com...
> I inherited a SQL Server 2000 database that has performance issues. I
> noticed the primary keys are set up as non-cluster indexes.
> By default the table primary key is created as cluster indexes. Could this
> cause a database performance problems if these are large tables and access
> often.
> If the table were set up with the primary key as a non-cluster index?
>
> Thanks,