July 15, 2010 at 9:18 pm
dear all,
i have a table with one primary key let say TableA and FieldA, i have created primary key as clustered and one index. but it is very slowly. Is there a mistake in this structure? Do I have create index as unique index? Table A have any records. Will it made a probelm when i create index on it? please share, i'm a newbie in DBA. big many thanks
July 15, 2010 at 10:21 pm
A primary key is unique. Is your one index also on FieldA or on another column? If it's on FieldA, then remove the index as it's a duplicate of the PK.
Please explain what is slow. Is it a query? If so, can you post the query so that we can help optimize it?
Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
Ramblings of a DBA (My SQL Server Blog)[/url]
Subscribe to my blog
July 16, 2010 at 1:24 am
i have remove the index. and it is still slow. from my app, i go to the next record it takes a long time than usuall..my structure is FieldA as clustered index. whta should i do next?
July 16, 2010 at 2:33 am
Please post table definitions, index definitions and execution plan, as per http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply