Prev: Transactional Replication (with Update) problem
Next: Howto find the Name of Logreader and Distribution Task
From: Hilary Cotter on 20 Nov 2009 07:48
Look at this:


http://msdn.microsoft.com/en-us/library/ms146910.aspx

http://msdn.microsoft.com/en-us/library/ms147890.aspx

"I would like a replication that not ex"
<Iwouldlikeareplicationthatnotex(a)discussions.microsoft.com> wrote in message
news:8F6B443A-8E35-491D-9F71-89AA8838560A(a)microsoft.com...
> Thanks a lot for your rapid reponse.
>
> Please How can I Create code to pull/push myagent and programmatically
> send
> the user a message.
>
> I am so sorry by I don't know how?
>
> Thanks for your great help.
>
> "Hilary Cotter" wrote:
>
>> If they are not connected during this period their subscription will
>> expire
>> and you will need to reinitialize.
>>
>> You can write code to pull/push your agent and then programmatically send
>> the user a message when it is done.
>>
>> Hilary
>> "I would like a replication that not ex" <I would like a replication
>> that
>> not ex(a)discussions.microsoft.com> wrote in message
>> news:FEBC61BF-AA6C-4BCB-A7BC-887D602A5D43(a)microsoft.com...
>> >
>> > Thank you for your response.
>> >
>> > I would like to ask about the maximum period; is it only 336 hours.
>> > In fact, subscribers may be not connected more than this period.
>> > Moreover,
>> > when I execute "use sp_changepublication
>> > 'PublicationName','retention',336
>> > "
>> > is this enable publication when connection returns.
>> >
>> > My problem is: I am using SQL 2000, I would like to perform a
>> > replication
>> > between many subscribers. Changes in databases are done by these
>> > subscribers.
>> > At this time, connection between subscribers and editor/publisher is
>> > not
>> > established. When they decide to send replication, they establish
>> > connection.
>> > Then they disconnect after the replication is done. This process will
>> > be
>> > iteratively repeated each time when they decide to send new updates in
>> > databases.
>> > I have the idea of keeping the replication looping until the connection
>> > is
>> > established.
>> > Another question: how can I be informed that the replication is done
>> > successfully? I would like to have a message like net send to inform
>> > users
>> > that jobs are done and they can disconnect.
>> >
>> > Thnaks a lot.
>> >
>> >
>> >
>> >
>> >
>> > "Hilary Cotter" wrote:
>> >
>> >> use sp_changepublication 'PublicationName','retention',336
>> >>
>> >> This value is in hours.
>> >>
>> >>
>> >> "wadii boulila" <boulila_wadii(a)yahoo.fr> wrote in message
>> >> news:88223b84f4f1443d9c097bdff9099146(a)newspe.com...
>> >> > I have performed a transactional replication in my company.
>> >> > However, all subscribers are not always connected to the
>> >> > editor/publisher.
>> >> > I have this error: NoSync subscriptions will need to be dropped and
>> >> > recreated. (Source: MSSQLServer, Error number: 21074).
>> >> > I know that is related to the Maximum Retention period of the
>> >> > distributor.
>> >> > But I would like to change this time and let the publication not
>> >> > expired
>> >> > for
>> >> > the maximum possible time.
>> >> >
>> >> > Thanks a lot for helping me.
>> >> >
>> >> > url:http://www.ureader.com/gp/1156-1.aspx
>> >>
From: Paul Ibison on 21 Nov 2009 10:50
One thing to be very wary of - if you want subscriptions to be ok after
being offline for a long time, you'll also need to change the distribution
retention period (sp_changedistributiondb).

However, if both the publication setting and the distribution setting are a
high number then you'll avoid the initial problem - expiring subscribers -
but potentially create a huge problem for other subscribers. Your
distribution database could "explode" in size as the Distribution Cleanup
Agent won't be able to remove the replication commands until the subscribers
have all synced up.
HTH,
Paul Ibison

From: Paul Ibison on 21 Nov 2009 10:53
If you want to do this in TSQL, you could use sp_start_job to run the agent.
To check connectivity try to run sp_who2 on a linked server to the
publisher, with some error handling. Net Send could be done using
sp_cmdshell, or you could send an email notification.
HTH,
Paul Ibison

First  |  Prev  | 
Pages: 1 2
Prev: Transactional Replication (with Update) problem
Next: Howto find the Name of Logreader and Distribution Task