3.2 Compound Keys Still a Problem?

Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
edited December 15, 2003 8:19AM in SQL Data Compare Previous Versions
Hi Grant,

If one of the PKs are of the datatype 'smallint', you could be seeing a
bug in SQL Data Compare 3.2. Try doing a 'check for updates' and get version
3.3, which has a fix for the problem.

Please let me know if I'm wrong in any way.

Thanks,

Brian Donahue
Red Gate Technical Support

"Grant Fritchey" <grant.fritchey@fmglobal.com> wrote in message
news:Ggx3P0AuDHA.1264@server53...
> Hello,
>
> I know in the initial release of 3.0 that compound primary keys created
> problems in the tool. We've just run into a problem in 3.2 where a table
has
> a two column primary key defined. We're seeing three records that are
> missing between tables showing up as changes and three records that are
> changes showing up as inserts.
>
> The exact version is 3.2.0.178. Any help here, or is more detail needed?
>
> Thanks,
>
> Grant
>
>
· Share on Twitter

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    Hi Grant,

    Great! Thanks for getting in touch...

    Brian Donahue

    "Grant Fritchey" <grant.fritchey@fmglobal.com> wrote in message
    news:wog0mk%23vDHA.304@server53...
    > Thanks,
    >
    > That does seem to have fixed the issue.
    >
    > Grant
    >
    > "Brian Donahue (Red Gate)" <brian.donahue@red-gate.com> wrote in message
    > news:7CduZubuDHA.1600@server53...
    > > Hi Grant,
    > >
    > > If one of the PKs are of the datatype 'smallint', you could be
    seeing
    > a
    > > bug in SQL Data Compare 3.2. Try doing a 'check for updates' and get
    > version
    > > 3.3, which has a fix for the problem.
    > >
    > > Please let me know if I'm wrong in any way.
    > >
    > > Thanks,
    > >
    > > Brian Donahue
    > > Red Gate Technical Support
    > >
    > > "Grant Fritchey" <grant.fritchey@fmglobal.com> wrote in message
    > > news:Ggx3P0AuDHA.1264@server53...
    > > > Hello,
    > > >
    > > > I know in the initial release of 3.0 that compound primary keys
    created
    > > > problems in the tool. We've just run into a problem in 3.2 where a
    table
    > > has
    > > > a two column primary key defined. We're seeing three records that are
    > > > missing between tables showing up as changes and three records that
    are
    > > > changes showing up as inserts.
    > > >
    > > > The exact version is 3.2.0.178. Any help here, or is more detail
    needed?
    > > >
    > > > Thanks,
    > > >
    > > > Grant
    > > >
    > > >
    > >
    > >
    >
    >
    · Share on Twitter
This discussion has been closed.