> Server statement trigger performs row-actions when the primary key was
> updated (lining up those INSERTED and DELETED rows may prove
> difficult...). Having to do a JOIN on the transition tables to get to rows
> is just nastily inefficient and can be outright wrong.
A reason why the majority of SQL Server folks use a surrogate key in way of
IDENTITY - imutable.
--
Tony Rogerson, SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson
[Ramblings from the field from a SQL consultant]
http://sqlserverfaq.com
[UK SQL User Community]
Received on Wed Aug 22 2007 - 00:56:05 CDT
