the question's table design is ugly as

1. person.id is not IDENTITY, so the caller must ensure uniqueness (e.g. sequence)

2. the person.name is not explicitly NOT NULL

3. the NIX_Person_ID_Name UI is...

if you already have SQL2008SP2 with some Cumulative Update Pack (CUP) you should not apply SP3

but now that MS have released the first CUP to SP3, you are good to...

if trying to find different/missing rows across 2 tables (writers suggested use of INTERSECT), I have always used OUTER JOIN (or FULLJOIN) constructs [on all SQL versions], such as

declare

The date datatype was added in SQL2008, so question might have been been better if it used the ubiquitous datetime datatype instead (i.e. viable on SQL2000, 2005 etc). No biggie!