Comments
1 comment
-
Hi James,
Unfortunately, even after many minutes of toil in my laboratory, I can't
find a situation that reproduces this behaviour.
Can you send a script of the triggers to support@red-gate.com?
Thanks,
Brian Donahue
Red Gate Technical Support
"James D. Albert" <james_albert@scantron.com> wrote in message
news:bWGoI%23uLDHA.1424@server53...
> "Ignore SET statements" is unchecked; QUOTED_IDENTIFIER is ignored.
>
> Suggestions?
>
> "Brian Donahue (Red Gate)" <brian.donahue@red-gate.com> wrote in message
> news:Guq5sRBLDHA.1424@server53...
> > Hi James,
> >
> > 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.
> >
> > Brian Donahue
> > Red Gate Technical Support
> >
> > "James D. Albert" <james_albert@scantron.com> wrote in message
> > news:knyr5eTKDHA.1176@server53...
> > > 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
> > views
> > > in SQL Server 2000. Is there a workaround?
> > >
> > >
> >
> >
>
>
Add comment
Please sign in to leave a comment.
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.
Brian Donahue
Red Gate Technical Support
"James D. Albert" <james_albert@scantron.com> wrote in message
news:knyr5eTKDHA.1176@server53...
> 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
views
> in SQL Server 2000. Is there a workaround?
>
>