hello, I need to replicate data in several clients of SQL server. The
replication I do it by means of a dynamic filter, according to suser_sname.
The problem is that I need the client can change the user and replicate
another data set, but only the created new data from last time that the
same user executed the replication (possibly in another client). how it
could make this?
I think what you are talking about is called realignments.
This is where a salesman is getting a subscription based on a filter which
only gives him data for his clients, ie the filter is on Salesman_A. You
want him to be able to now get only Salesman_B's data.
Your best bet is probably to drop the subscription and create a new dynamic
subscription and this time perhaps filter on hostname and hardcode the value
of the HostName parameter in the merge agent as Salesman_B.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Toms Hernndez" <tomihernandez@.yahoo.es> wrote in message
news:OK4lkRNwEHA.3320@.TK2MSFTNGP14.phx.gbl...
> hello, I need to replicate data in several clients of SQL server. The
> replication I do it by means of a dynamic filter, according to
suser_sname.
> The problem is that I need the client can change the user and replicate
> another data set, but only the created new data from last time that the
> same user executed the replication (possibly in another client). how it
> could make this?
>
|||Yes I could drop and recreate a new dynamic subscription with other
user. But my problem is replicate only the new data from the last
replication by this user,
although it does not have in local the previous data because this
replication became in another client.
Are you understand my problem?
Thanks.
"Hilary Cotter" <hilary.cotter@.gmail.com> escribi en el mensaje
news:O6hqeeNwEHA.3296@.TK2MSFTNGP10.phx.gbl...
> I think what you are talking about is called realignments.
> This is where a salesman is getting a subscription based on a filter which
> only gives him data for his clients, ie the filter is on Salesman_A. You
> want him to be able to now get only Salesman_B's data.
> Your best bet is probably to drop the subscription and create a new
dynamic
> subscription and this time perhaps filter on hostname and hardcode the
value
> of the HostName parameter in the merge agent as Salesman_B.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Toms Hernndez" <tomihernandez@.yahoo.es> wrote in message
> news:OK4lkRNwEHA.3320@.TK2MSFTNGP14.phx.gbl...
> suser_sname.
>
|||Perhaps I don't understand your problem.
Is your problem that this laptop could have some recently entered data in,
and you want to sync it up to the publisher, before deploying your new
subscription?
If so, you could set the merge agent to run on a schedule (make sure you
remove the -Continuous switch) and run the merge agent a couple of times
before dropping the subscription.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Toms Hernndez" <tomihernandez@.yahoo.es> wrote in message
news:u$vJJmNwEHA.3840@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Yes I could drop and recreate a new dynamic subscription with other
> user. But my problem is replicate only the new data from the last
> replication by this user,
> although it does not have in local the previous data because this
> replication became in another client.
> Are you understand my problem?
> Thanks.
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> escribi en el mensaje
> news:O6hqeeNwEHA.3296@.TK2MSFTNGP10.phx.gbl...
which[vbcol=seagreen]
> dynamic
> value
replicate[vbcol=seagreen]
the[vbcol=seagreen]
it
>
|||no, I will try to explain,
The replication begin in the subscriber, it is a pull merge
subscription. And the data to replicate depends of the user (suser_sname)
who is selected in the start of an application. Today is John and tomorrow
is Charles the user, and the data set is different to download to the client
and I dont need to download all the data of Charles, I need only from a
date (the date of the last sync from Charles in this laptop or in the other
laptop).
Are you understand now?
"Hilary Cotter" <hilary.cotter@.gmail.com> escribi en el mensaje
news:O8KVfqNwEHA.3872@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Perhaps I don't understand your problem.
> Is your problem that this laptop could have some recently entered data in,
> and you want to sync it up to the publisher, before deploying your new
> subscription?
> If so, you could set the merge agent to run on a schedule (make sure you
> remove the -Continuous switch) and run the merge agent a couple of times
> before dropping the subscription.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Toms Hernndez" <tomihernandez@.yahoo.es> wrote in message
> news:u$vJJmNwEHA.3840@.tk2msftngp13.phx.gbl...
> which
You[vbcol=seagreen]
The
> replicate
> the
> it
>
