QUOTED_IDENTIFIER and triggers in 2.03
SQL Compare can also spot changes in the QUOTED_IDENTIFIER setting
between databases. It would not report them, however, if you've got 'Ignore
SET statements' set in the View Options.
Thanks for your post.
Red Gate Technical Support
"James D. Albert" <[email protected]> wrote in message
> If the "QUOTED_IDENTIFIER" option differs between two databases for a
> trigger, SQL Compare 2.03 doesn't appear to notice. This leads to trouble
> when the triggers are on tables that are somehow involved with indexed
> in SQL Server 2000. Is there a workaround?