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 |
|
MirandaJ
Starting Member
35 Posts |
 Posted - 2006-02-06 : 13:02:16
|
| We recently updated some of the databases from MS Access 2000 to SQL Server 2000. In Access we had columns which were set to Indexed No Duplicates, these were not Primary key fields. Is this possible to set some indexes to prevent duplicates in SQL Server without creating performance issues?Miranda |
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2006-02-06 : 13:57:53
|
| Unique Constraint is what you're looking for. BTW Joe, a clustered index (by itself) won't maintain uniqueness.EDIT:hmmm, there was a post by someone named Joe there a minute ago...Damn, is it time for my medication already?Be One with the OptimizerTG |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2006-02-06 : 19:29:59
|
| Does Access allow multiple rows with NULL when you set up the "Index No Duplicates"? Hopefully not, but if it does I'm afraid that SQL will only allow one row.Kristen |
|
|
|
|
|
|
Indexes