Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Ex
Posting Yak Master
166 Posts |
 Posted - 2005-01-09 : 17:20:22
|
| hey alljust wondering what my best option here would bei have a tablethat at the moment hasvalue1, value2, value3, value4, value5, value6where value1 is a Identity Coli have hadvalue2value3value4value5as a combind PKi need these 4 values to be unique and i shall be doing alot of joins using the identity column(value1)just wondering what i can do for efficency in reguards to indexes? clustered noncluserted? on the identity ? etc? any ideas |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2005-01-09 : 17:27:04
|
| A clustered index on the identity will save space but it might be more useful elsewhere.An identity always needs an unique index if you want it to be unique.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
keys and index's