One of my database engineer teammates put this little demo together, but she doesn’t blog so she let me most it here (thanks Y.L.!).
Sql_variant is a data type introduced in SQL Server 2008 which allows data of varying types to be stored in the same column in their native types. Despite its flexibility, sql_variant suffers from some misunderstanding and doesn’t find wide use.
One of the nuances of sql_variant is with unique constraints. Usually when we apply a unique constraint to a column which is of a single type so we don’t think about the comparison other than the value. However, when we use a sql_variant, uniqueness is determined by both value and type.
To put this to the test, you can run this little experiment in any version of SQL Server since 2008:
CREATE table #test (GCId SQL_VARIANT, name VARCHAR(10))
CREATE UNIQUE NONCLUSTERED INDEX [UK_test ] ON #test
(
[GCId] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF,
IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 70)
GO
insert into #test (GCId, name)
values( ‘2009728366’, ‘varchar’)
insert into #test (GCId, name)
values( 2009728366, ‘bigint’)
SELECT *
FROM #test
–drop table #test
Even with the implicit conversion between bigint and varchar, you can still insert the same value as long as its a different type. Try re-running the insert and select statements again and see them both fail because the second attempt violates the unique constraint.
This is in no way meant to dissuade the use of sql_variant, but merely to point out one consideration regarding its use. When it comes to storing data, we need to store data in their correct type.