Possible Duplicate:
How do I create unique constraint that also allows nulls in sql server
I have a table where I need to force a column to have unique values. This column must be nullable and by business logic multiple NULL values should be permitted, whereas other duplicate values are not.
SQL Server UNIQUE constraint is no good in this situation because it considers NULL as regular values, so it will reject duplicate NULLs.
Currently, value uniqueness is granted by the BLL so I'm not looking for a dirty hack to make it work. I just would like to know if there is a clean solution to enforce this constraint in the DB.
And yeah, I know I can write a trigger to do that: is a trigger the only solution? (or the best solution anyway?)
If you're using SQL Server 2008, have a look into Filtered Indexes to achieve what you want.
For older version of SQL Server, a possible alternative to a trigger involves a computed column:
NULL
, otherwise it uses the value of the row's Primary Key column (or any column which will be unique).UNIQUE
constraint to the computed column.http://www.sqlmag.com/article/articleid/98678/sql_server_blog_98678.html
You should use UNIQUEIDENTIFIER in that column, can be NULL and also is unique by definition. Hope that helps.
You can create a view in which you select only not null values and create an index on it.
Here is the source - Creating Indexed Views
If you're using SQL Server 2008 (won't work for earlier version) there is the concept of a filtered index. You can create the index on a filtered subset of the table.
Duplicate of this question?
The calculated column trick is widely known as a "nullbuster"; my notes credit Steve Kass:
Works on SQL Server 2000. You may need
ARITHABORT
on e.g.