That confirms my thinking
Further to my comments earlier, I have also seen that on occasions I get ALL
of these changes as inserts, but do not have that many rows on my subscriber.
Typical numbers are that I would expect about 3000 to 4000 rows in an
initialise. I get (consistently across all tables) 52 times that amount. And
as mentioned above I have seen the initialisation pass down 88000 inserts.
Some mystery indeed. Currently I am looking at the various parameters used
in creating the publication and the articles to seee if this has caused
something unexpected.
[quoted text, click to view] "Hilary Cotter" wrote:
> Depending on your join filters, the individual subscriber should only get
> rows which are part of his/her filter partition. It sounds like something is
> wrong here.
Depending on your join filters, the individual subscriber should only get
rows which are part of his/her filter partition. It sounds like something is
wrong here.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com [quoted text, click to view] "SteveM" <SteveM@discussions.microsoft.com> wrote in message
news:DF9E61F2-2691-467C-9259-B6D2B4E08349@microsoft.com...
>I have a merge replication scenario where the technicians are filtered by
> their individual codes. Each technician has his own mobile device for
> collecting and synchronising data.
>
> On initialisation of the subscription, the user should only get the data
> that is relevant to their code.
>
> The client is staging the rollout to all of their technicians and as the
> system has grown, we have noticed that there are a number (getting larger
> every day) of updates that are creeping into the initialisation of each
> subscription.
>
> My understanding is that an initialisation will only ever apply the
> inserts
> necessary to create the subscriber database.
>
> Is my understadning incorrect?
>
> Is the some parameter in the creation of the publication that we have set
> incorrectly?
>
> Is there something wrong with SQLServer 2005 itself?
>
>
> I am very interested to hear anyones comments or advice around this issue.
>
> Thanks
> Steve
