Nils Gustav Stråbø (10/19/2012)

---

Aaaaarg!!! Got it wrong because of the unclustered index options.

I know that SQL Server enforces unique constraints by creating unique indexs, but I wasn't sure if this was what the author meant.

ako58 (10/19/2012)

---

Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2)

DECLARE @t TABLE (id INT IDENTITY,
id1 INT CHECK (id>id1))

Msg 8141, Level 16, State 0, Line 1
Column CHECK constraint for column 'id1' references another column, table '@t'.

DECLARE @t TABLE (id INT IDENTITY,
 id1 INT, CHECK (id>id1))

create TABLE t(id INT IDENTITY,
 id1 INT CHECK (id>id1))

 create TABLE #t(id INT IDENTITY,
 id1 INT CHECK (id>id1))

Nils Gustav Stråbø (10/19/2012)

---

Aaaaarg!!! Got it wrong because of the unclustered index options.

I know that SQL Server enforces unique constraints by creating unique indexs, but I wasn't sure if this was what the author meant.

A minor detail; You probably mean ROGUIDCOL, not ROWGUID.