FKs not dropped before PKs

Brian Donahue

Hi JW,

You're 100% correct. This is a known issue and it's been fixed for the
upcoming release that you can look forward to in two weeks or so.

Regards,

Brian Donahue
Red Gate Technical Support

"JW" <sorrynospam@nospamforme.com> wrote in message
news:s7E3v%23W8DHA.1468@server53...
> A point of clarification. The FK constraints reference and therefore are
> dependent upon the PK constraint that is being dropped. So the script
> fails.
>
> "JW" <sorrynospam@nospamforme.com> wrote in message
> news:793ms4W8DHA.2200@server53...
> > I'm evaluating SQL Compare 3.1.0.151. I performed a complete compare
and
> > discovered differences in the primary key constraint names. The synch
> > script that was created failed to drop the Foreign Key constraints prior
> to
> > dropping and recreating the PK constraints. The option to "include
> > dependent database objects" was selected.
> >
> > I thought I saw a previous acknowledgement on this forum that this was a
> > known issue--but can no longer find that thread. If this is a known
> issue,
> > do you have an estimate on when a fix might be available.
> >
> > Thanks!
> >
> >
>
>

Brian Donahue

This issue had been fixed in version 3.15 and is no longer 'live'.