Plannig indexing

[Dany13]

Dear all.
I am designing the database for SQL server 2005 . I have problem in planning index.
In one part I have personal table. I don’t need quarry by personal ID any time but I create clustered index in personal ID by add primary key constraint .
I decide have to clustered index constraint in other column for example last name or SSN and add none clustered index for primary key.
I need some Idea about this.
Thank you , Saeid.

[r035198x]

...I don’t need quarry by personal ID any time but I create clustered index in personal ID by add primary key constraint .
...

Are you sure about this? Don't you have personalID appearing as a foreign key in other tables?

[Dany13]

i use PersonalID for foreign key but for this propose I can add non clustered index .
By this work sort data in table in insert time and increase quarry performance.
it is right?

[r035198x]

i use PersonalID for foreign key but for this propose I can add non clustered index .
By this work sort data in table in insert time and increase quarry performance.
it is right?

Not sure I understand what you are trying to say but I think this article should be able to help you more.

[ck9663]

Indexing,makes accessing tables faster, that's a general rule.

If the table will only have one index, make it clustered.

Create a clustered index for your primary key and create non-clustered for those columns frequently use in WHERE conditions on your query. Though re-indexing is a 3GL thing, (dbase, foxpro, foxbase) it wouldn't hurt to do a index maintenance whenever your data increases by at least 10-15%.

-- CK