2 possible bugs in SQL Compare v2.03
The second issue is easy to fix. It should compare cascading update and
delete settings properly if the 'Create SQL 7 compatible scripts' option is
The first issue, I'll have to look a little deeper into. It could be an
oversight, or there could be a legitimate reason for it.
Red Gate Technical Support
"Rich Klein" <[email protected]> wrote in message
> We have encountered two different problem scenarios while using SQL
> 1) Comparing triggers owned by a user other then 'dbo'. The generated
> TRIGGER statement in the update script does not qualify the trigger name
> with its owner. So if the trigger is owned by 'joe', but the update is
> by 'dbo', it fails.
> 2) Comparing foreign key constraints where the first is set to CASCADE
> DELETE or CASCADE UPDATE, and the second is not, they will show up as '='
> the Compare even though they are not.
> Are these known issues?