QUOTED_IDENTIFIER and triggers in 2.03

Brian DonahueBrian Donahue Posts: 6,590 New member
edited June 11, 2003 1:00PM in SQL Compare Previous Versions
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" <[email protected]> wrote in message
news:[email protected]
> 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?
>
>

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 New member
    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 [email protected]?

    Thanks,
    Brian Donahue
    Red Gate Technical Support

    "James D. Albert" <[email protected]> wrote in message
    news:bWGoI%[email protected]
    > "Ignore SET statements" is unchecked; QUOTED_IDENTIFIER is ignored.
    >
    > Suggestions?
    >
    > "Brian Donahue (Red Gate)" <[email protected]> wrote in message
    > news:[email protected]
    > > 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" <[email protected]> wrote in message
    > > news:[email protected]
    > > > 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?
    > > >
    > > >
    > >
    > >
    >
    >
This discussion has been closed.