Re: ErWin triggers and mutating tables

From: hazledid <david.hazledine_at_roche.com>
Date: Thu, 29 Apr 1999 10:09:28 GMT
Message-ID: <sdWV2.1099$vY2.13966@c01read01.service.talkway.com>

I'm not familiar with ERwin or SQL Server, but it sounds as if you're using
triggers to enforce referential integrity. If so, how about getting ERwin
to enforce RI with declarative DDL instead (i.e., explicit FOREIGN KEY constraints). That should fix your problem.

That said, if you didn't have explicit foreign keys in your SQL Server database, and ERwin is simply reverse engineering the triggers it finds, then I guess there's no way of automatically switching from trigger enforcement to declarative enforcement.

--

David J. Hazledine
Roche Products Limited
40 Broadwater Road
Welwyn Garden City
AL7 3 AY
Registration Number 100674
(david.hazledine_at_roche.com)
--

Posted via Talkway - http://www.talkway.com Exchange ideas on practically anything (tm). Received on Thu Apr 29 1999 - 05:09:28 CDT