Re: Replication Conflict Viewer crashes
From: Michael \(michka\) Kaplan [MS] (michkap_at_online.microsoft.com)
Date: 05/20/04
- Previous message: Bruce: "Re: Replication Conflict Viewer crashes"
- In reply to: Bruce: "Re: Replication Conflict Viewer crashes"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 20 May 2004 09:27:25 -0700
"Bruce" <bruce@aristotle.net> wrote...
> > How many fields in the table?
>
> There are 172 fields in the table.
This would be the main source of there being a problem. Which is not to say
it wouldn't still be a bug. But the bulk of the testing was done on much
more reasonably sized (and often properly normalized) schemas.
> The option to show only the
> conflicting fields is selected.
Note that this means the viewer has to load every item and compare them to
see if they are the same or not. Depending on the complexity of the fields
and the amount of change, the time it takes to "compare every item and
display the changed ones" vs. "display every item" can vary in terms of
which is more intensive.
My advice would be to do some schema design, specifically to properly
normalize the data, as a design that is so far from 3NF as to have tables
with 172 columns in them is fraught with either unnecessary duplication,
wasted space, and/or data inconsistencies which replication will only be
hurt by.
-- MichKa [MS] NLS Collation/Locale/Keyboard Development Globalization Infrastructure and Font Technologies This posting is provided "AS IS" with no warranties, and confers no rights.
- Previous message: Bruce: "Re: Replication Conflict Viewer crashes"
- In reply to: Bruce: "Re: Replication Conflict Viewer crashes"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|