Push-Replication with Internet-Connection

I read several articles to this topic, and I couldnt understand, why
a SQL-Server-Subscriber need to connect to the distributor.
- I have a Server A in my LAN, publishing a Database, distributor is
the same Server A.
- using Push-Merge-Replikation
- Server B in the internet, behind a firewall
In http://support.microsoft.com/kb/321822 you can read, that you the 2
servers must be able to ping eachother.
Is this definitely true? The Merge-Agent is running on Server A, and
Server A can connect to Server B. Why does the subscriber B need to
connect to Server A?
If you would use Pull-Replication, and der Merge-Agent was running on
Server B, yes, then I could unterstand this.
If this fact is really true, then it is much more difficult to realize
such a default-scenario like I would like to use.
Andreas Lauffer, Germany
You will need connectivity at some point in time. Your subscriber can be
offline for long periods of time, but at some point in time, it must sync
with the publisher.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Now available on Amazon.com
http://www.amazon.com/gp/product/off...?condition=all
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Andreas Lauffer" <al@.lauffers.de> wrote in message
news:u1ie01tic78r09tpmdjl3vuusmk9om6c78@.4ax.com...
> I read several articles to this topic, and I couldnt understand, why
> a SQL-Server-Subscriber need to connect to the distributor.
> - I have a Server A in my LAN, publishing a Database, distributor is
> the same Server A.
> - using Push-Merge-Replikation
> - Server B in the internet, behind a firewall
> In http://support.microsoft.com/kb/321822 you can read, that you the 2
> servers must be able to ping eachother.
> Is this definitely true? The Merge-Agent is running on Server A, and
> Server A can connect to Server B. Why does the subscriber B need to
> connect to Server A?
> If you would use Pull-Replication, and der Merge-Agent was running on
> Server B, yes, then I could unterstand this.
> If this fact is really true, then it is much more difficult to realize
> such a default-scenario like I would like to use.
>
> Andreas Lauffer, Germany
>
>
|||Sure you need a connection at one time. But the question is in which
direction you need to connect.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:<uuQaNsZDFHA.1936@.TK2MSFTNGP14.phx.gbl>...[vbcol=seagreen]
> You will need connectivity at some point in time. Your subscriber can be
> offline for long periods of time, but at some point in time, it must sync
> with the publisher.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Now available on Amazon.com
> http://www.amazon.com/gp/product/off...?condition=all
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Andreas Lauffer" <al@.lauffers.de> wrote in message
> news:u1ie01tic78r09tpmdjl3vuusmk9om6c78@.4ax.com...

Push Subscription Connection Fails

I cannot get internet connection to work for push subscription to transactional publication.

Publisher/distributor: SQL Server 2000
Subscriber: SQL Server 2000
Connection: TCP/IP, SQL Authentication. Works fine from SQLEM or Query Analyzer.
Subscription: push, transactional, schema/data already initialized.

When I run distributor agent fails with "The process could not connect to subscriber 'TEST'", error "Server does not exist or access denied".

Agent output does not give anything more specific. It fails after...
Connecting to Subscriber 'TEST'
Connecting to Subscriber 'TEST.REPL'

Profiler shows nothing happening at all.

If change subscriber setup on distributor to use trusted connection instead of SQL Auth it works fine.

Any ideas?OK, so all the replication experts are on vacation this week but I eventually managed to figure it out myself.

When defining subscribers (through 'distributor properties') use the subscriber TCP/IP address directly and not a server alias like I was doing. Silly Billy!

Push Agent limits at Central Distributor

How many Distributor Agents (Distrib.exe files) SQL Server 2000 work better?
There is any limits?
Message posted via http://www.droptable.com
I'm not aware of any limits. For me, the issue is one of ordering of
transactions and isolation of publications. IE if you use a shared agent,
the transaction order is maintained which is not the case with independant
agents. The flipside is that an error which stops the shared agent will stop
it delivering transactions for all its publications until it is fixed.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I've scaled it beyond 200, but that was with a pull, not a push. You get
better scalability with a pull. When you start approaching high numbers you
need to tweak this key.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\SQL2000\SQLServerAgent\Subsystems\Distribut ion and set the value
C:\Program Files\Microsoft SQL
Server\MSSQL$SQL2000\BINN\SQLREPSS.DLL,C:\Program Files\Microsoft SQL
Server\80\COM\DISTRIB.EXE,ReplStart,ReplEvent,Repl Stop,100
where you Modify 100 to be the number of simultaneous distribution agents
you expect.
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
"Krisnamourt via droptable.com" <u21487@.uwe> wrote in message
news:66e155dcf7428@.uwe...
> How many Distributor Agents (Distrib.exe files) SQL Server 2000 work
> better?
> There is any limits?
> --
> Message posted via http://www.droptable.com
>

Pull replication setup problem

Hi,
I am changing the scenario of our replication from Push to Pull, but I could
not set up the Pull replication.
The publisher and distributor are on the same machine.
The subscriber always gets an error message as
"The process could not read file
"E:\repl\unc\MyServer_MyDB\200508\tableone.sch " due to OS error 3.
I searched a lot on the google, but no one seems fit my problem.
I am using SQL Server 2000 on both the Publisher and Subscriber.
Thanks for any help
Frank
Frank,
can you log on to the subscriber using the sql server agent's login and see
if you can read the snapshot share?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Pull replication

I cannot get a pull merge replication to work.
The distributor is Win2000 running SQL 2000.
Subscribers are XP Pro running MSDE.
Agent command:
-Publisher [DistSVR] -PublisherDB [MyDB] -Publication [MyDB] -Subscriber
[SubSVR] -SubscriberDB [MyDB] -SubscriptionType 1 -SubscriberSecurityMode 0
-SubscriberLogin [sa] -SubscriberEncryptedPassword
[??????] -Distributor [DistSVR]
The errors:
Category:AGENT
Source: SubSVR
Number: 20084
Message: The process could not connect to Subscriber 'SubSVR'.
Category:SQLSERVER
Source: SubSVR
Number: 17
Message: SQL Server does not exist or access denied.
Thank you ver much.
This means your subscriber can't connect.
Log on to your subscriber machine and try to ping your publisher.
Also verify you can ping your subscriber using the host name SubSVR from
your subscriber. Also verify that your subscriber password is correct.
Hilary Cotter
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
"Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
news:C60CE48B-18A5-4C03-A034-5FF59E876951@.microsoft.com...
> I cannot get a pull merge replication to work.
> The distributor is Win2000 running SQL 2000.
> Subscribers are XP Pro running MSDE.
> Agent command:
> -Publisher [DistSVR] -PublisherDB [MyDB] -Publication [MyDB] -Subscriber
> [SubSVR] -SubscriberDB [MyDB] -SubscriptionType 1 -SubscriberSecurityMode
0
> -SubscriberLogin [sa] -SubscriberEncryptedPassword
> [??????] -Distributor [DistSVR]
> The errors:
> Category:AGENT
> Source: SubSVR
> Number: 20084
> Message: The process could not connect to Subscriber 'SubSVR'.
> Category:SQLSERVER
> Source: SubSVR
> Number: 17
> Message: SQL Server does not exist or access denied.
> Thank you ver much.
>
|||Thank you for your reply.
Subscriber PC name and SQL server name are different. It's the reason ?
Excuse me for the question: SubscriberLogin is the login to Subscriber or
Distributer ?
Thank you.
"Thang Long" wrote:

> I cannot get a pull merge replication to work.
> The distributor is Win2000 running SQL 2000.
> Subscribers are XP Pro running MSDE.
> Agent command:
> -Publisher [DistSVR] -PublisherDB [MyDB] -Publication [MyDB] -Subscriber
> [SubSVR] -SubscriberDB [MyDB] -SubscriptionType 1 -SubscriberSecurityMode 0
> -SubscriberLogin [sa] -SubscriberEncryptedPassword
> [??????] -Distributor [DistSVR]
> The errors:
> Category:AGENT
> Source: SubSVR
> Number: 20084
> Message: The process could not connect to Subscriber 'SubSVR'.
> Category:SQLSERVER
> Source: SubSVR
> Number: 17
> Message: SQL Server does not exist or access denied.
> Thank you ver much.
>

Pull or push subscription?

Faustino,
I agree about pull, and you might also want to
investigate a remote distributor to offload production
server processing, especially if you are using
transactional replication.
HTH,
Paul Ibison
The problem with pull subscriptions is that you no longer have a central
point of administration.
What this means is that if a pull subscription agent fails you will not see
the error on your publisher, but will have to visit the subscriber to see
this error. To get around this use replication monitor group and add all the
subscribers to it.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:3ec801c48ff9$11379320$a601280a@.phx.gbl...
> Faustino,
> I agree about pull, and you might also want to
> investigate a remote distributor to offload production
> server processing, especially if you are using
> transactional replication.
> HTH,
> Paul Ibison
|||Actually we are planning to do a merge replication with all sites. It is the
database for an order processing system. Each branch will be feeding us with
the orders and we will sent them price changes etc.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:3ec801c48ff9$11379320$a601280a@.phx.gbl...
> Faustino,
> I agree about pull, and you might also want to
> investigate a remote distributor to offload production
> server processing, especially if you are using
> transactional replication.
> HTH,
> Paul Ibison

Publishing data while using same server as distributor

Hi all,
I am trying to publish data making the same server as Distributor while
using the wizard it says i am using "sa" account and the server cannot be
used as a distributor if i use "sa" account,how do i go around this? do i
need to stop the server and start with a different account? and setup server
agent to use other account ?
Can anyone clear my doubts?
Thanks
Sudha
Does it say "Local System" or "sa" I have never heard of it having a problem
with the sa account but I have when it uses the local system account. Can
you ensure that your SQL Server service account is running under a domain
account? Make this change through enterprise manager.
Hilary Cotter
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
"sudha" <sudha@.discussions.microsoft.com> wrote in message
news:9DA7173A-C32D-4953-9453-8AEE0656F752@.microsoft.com...
> Hi all,
> I am trying to publish data making the same server as Distributor while
> using the wizard it says i am using "sa" account and the server cannot be
> used as a distributor if i use "sa" account,how do i go around this? do i
> need to stop the server and start with a different account? and setup
server
> agent to use other account ?
> Can anyone clear my doubts?
> Thanks
> Sudha
|||Hi Hilary,
I appreciate your reply. Yes it says "SQL Server Agent on "servername" uses
System Account,which causes replication between servers to fail.
You suggested me to change,sql service account ,how do i change it and do i
need to stop and start the server after i make a change?
I will be thankful if i can get this answer.
Sudha
"Hilary Cotter" wrote:

> Does it say "Local System" or "sa" I have never heard of it having a problem
> with the sa account but I have when it uses the local system account. Can
> you ensure that your SQL Server service account is running under a domain
> account? Make this change through enterprise manager.
> --
> Hilary Cotter
> 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
> "sudha" <sudha@.discussions.microsoft.com> wrote in message
> news:9DA7173A-C32D-4953-9453-8AEE0656F752@.microsoft.com...
> server
>
>
|||Right click on EM, select Properties, click on the security tab and its at
the bottom - yes there will be a restart.
Hilary Cotter
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
"sudha" <sudha@.discussions.microsoft.com> wrote in message
news:9B912EFE-BF61-4C57-B7A1-2F35F430B5D7@.microsoft.com...
> Hi Hilary,
> I appreciate your reply. Yes it says "SQL Server Agent on "servername"
uses
> System Account,which causes replication between servers to fail.
> You suggested me to change,sql service account ,how do i change it and do
i[vbcol=seagreen]
> need to stop and start the server after i make a change?
> I will be thankful if i can get this answer.
> Sudha
> "Hilary Cotter" wrote:
problem[vbcol=seagreen]
Can[vbcol=seagreen]
domain[vbcol=seagreen]
while[vbcol=seagreen]
cannot be[vbcol=seagreen]
do i[vbcol=seagreen]
|||Hi Hilary,
Thanks for your response again but in my EM in the Security Tab of database
properties the server agent account start up options frame is disabled,why is
it? and what do i do with it?
thanks
sudha
"Hilary Cotter" wrote:

> Right click on EM, select Properties, click on the security tab and its at
> the bottom - yes there will be a restart.
> --
> Hilary Cotter
> 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
> "sudha" <sudha@.discussions.microsoft.com> wrote in message
> news:9B912EFE-BF61-4C57-B7A1-2F35F430B5D7@.microsoft.com...
> uses
> i
> problem
> Can
> domain
> while
> cannot be
> do i
>
>
|||You need to set up a domain user account for your sql
server service and sql server agent. Editing the startup
properties in EM won't give you the option to browse AD,
so it's easiest to do this in Control Panel,
Administratove Tools, Services.
Have a look for MSSQLSERVER, SQLSERVERAGENT. For
replication purposes we are almost always just concerned
with the latter service. From the ideal DBA point of
view, you should change them both, however. To make
things simple, select the same domain user for both
services, and this account must be a local administrator.
If not, you'll end up editing permissions on various
registry keys, and you really don't want to have to do
this. After you've restarted, it should all be tickety-
boo.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

>--Original Message--
>Hi Hilary,
>Thanks for your response again but in my EM in the
Security Tab of database
>properties the server agent account start up options
frame is disabled,why is[vbcol=seagreen]
>it? and what do i do with it?
>thanks
>sudha
>"Hilary Cotter" wrote:
security tab and its at[vbcol=seagreen]
message[vbcol=seagreen]
2F35F430B5D7@.microsoft.com...[vbcol=seagreen]
Agent on "servername"[vbcol=seagreen]
servers to fail.[vbcol=seagreen]
do i change it and do[vbcol=seagreen]
change?[vbcol=seagreen]
heard of it having a[vbcol=seagreen]
local system account.[vbcol=seagreen]
running under a[vbcol=seagreen]
manager.[vbcol=seagreen]
message[vbcol=seagreen]
8AEE0656F752@.microsoft.com...[vbcol=seagreen]
server as Distributor[vbcol=seagreen]
account and the server[vbcol=seagreen]
do i go around this?[vbcol=seagreen]
different account? and setup
>.
>
|||Thanks Paul,
I will try out the things which you have suggested and let you know if i am
fine.
Great to know how things get fixed and from which places.The more we try to
dig the more we are ignorant.Thanks for giving me the information.
Sudha
"Paul Ibison" wrote:

> You need to set up a domain user account for your sql
> server service and sql server agent. Editing the startup
> properties in EM won't give you the option to browse AD,
> so it's easiest to do this in Control Panel,
> Administratove Tools, Services.
> Have a look for MSSQLSERVER, SQLSERVERAGENT. For
> replication purposes we are almost always just concerned
> with the latter service. From the ideal DBA point of
> view, you should change them both, however. To make
> things simple, select the same domain user for both
> services, and this account must be a local administrator.
> If not, you'll end up editing permissions on various
> registry keys, and you really don't want to have to do
> this. After you've restarted, it should all be tickety-
> boo.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
> Security Tab of database
> frame is disabled,why is
> security tab and its at
> message
> 2F35F430B5D7@.microsoft.com...
> Agent on "servername"
> servers to fail.
> do i change it and do
> change?
> heard of it having a
> local system account.
> running under a
> manager.
> message
> 8AEE0656F752@.microsoft.com...
> server as Distributor
> account and the server
> do i go around this?
> different account? and setup
>

Publishing a subscriber...

Hello...
I am looking to see if it is possible to publish a subscriber... so i have
the following:
publisher -> distributor -> subscriber
What I want is
publisher -> distributor -> subscriber (now a publisher as well) ->
distributor -> new subscriber
Is this possible? Has anyone had experience with this? All servers are SQL
Server 2000.
Please advise...
Thanks,
Brett
Brett,
please have a look here:
http://www.replicationanswers.com/Republishing2005.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||It is possible, and infact recommended when you are using merge replication.
However you should ensure that the remote distributor is clustered as this
introduces a single point of failure.
Remote distributors are more critical in high volume transactional
replication topologies. They are unnecessary in merge replication.
Hilary Cotter
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
"Brett Davis" <sqlsquirrel@.msn.com> wrote in message
news:efumTHWRHHA.3412@.TK2MSFTNGP02.phx.gbl...
> Hello...
> I am looking to see if it is possible to publish a subscriber... so i have
> the following:
> publisher -> distributor -> subscriber
> What I want is
> publisher -> distributor -> subscriber (now a publisher as well) ->
> distributor -> new subscriber
> Is this possible? Has anyone had experience with this? All servers are
> SQL Server 2000.
> Please advise...
> Thanks,
> Brett
>
|||On Jan 31, 12:01 pm, "Brett Davis" <sqlsquir...@.msn.com> wrote:
> Hello...
> I am looking to see if it is possible to publish a subscriber... so i have
> the following:
> publisher -> distributor -> subscriber
> What I want is
> publisher -> distributor -> subscriber (now a publisher as well) ->
> distributor -> new subscriber
> Is this possible? Has anyone had experience with this? All servers are SQL
> Server 2000.
> Please advise...
> Thanks,
> Brett
Brett;
I've got about 90 databases set up similar to this:
Publisher/Distributor -> Subscriber -> Distributor -> Subscriber
One thing that affected me is when setting up conflict resolution, I
had to select the decimal Priority figure before it would let me set
this up. This may just be because my publishers are using the desktop
version of MSSQL2K.
Another item that I am currently having trouble with is schema
changes. When I use the appropriate stored procedures to alter
tables, and then I restart the snapshot agent on the publishers, the
changes are propagated to the first subscriber, but they don't make it
to the second subscriber. I need to start another thread about
that. ;)
-Joseph

Publisher/Distributor

Hi,
I would like to hear opinion from experts.
Assume I have 3 warehouses and 1 Head office. I want to build a
centralized Subscriber. should i use
"3 Publishers/3 Distributors and 1 Subscriber" -- each sever will have 1 P
and 1 D
or
"3 Publishers and 1 Distributor and 1 Subscriber"
or
both way will work well...
Thanks
Ed
I would use 3 publishers and 3 local distributors (on the same box as the
three publishers).
Hilary Cotter
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
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:3A2A37F3-7254-4985-9B5F-A5A5C000F980@.microsoft.com...
> Hi,
> I would like to hear opinion from experts.
> Assume I have 3 warehouses and 1 Head office. I want to build a
> centralized Subscriber. should i use
> "3 Publishers/3 Distributors and 1 Subscriber" -- each sever will have 1
P
> and 1 D
> or
> "3 Publishers and 1 Distributor and 1 Subscriber"
> or
> both way will work well...
> Thanks
> Ed

publisher, distributor, subscriber all on one box?

has anyone done this? I need to test something and thought I would give
this a try...
tia
-comb
I do it all the time.
Hilary Cotter
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
"combfilter" <asdf@.adsf.com> wrote in message
news:MPG.1cfeab14ad684989697@.news.newsreader.com.. .
> has anyone done this? I need to test something and thought I would give
> this a try...
> tia
> -comb
|||In article <eU3NT3YYFHA.3584@.TK2MSFTNGP12.phx.gbl>,
hilary.cotter@.gmail.com says...
> I do it all the time.
>
so do i set it up just under the configure replication... in enterprise
manager? is there anything special i need to do? Is there a smarter
way to move tables from one db to another continually?
Thanks,
-comb
|||Yes, and what do you mean by move tables continuously? For this possibly log
shipping is the best as it will mirror objects with no intervention, but
your destination will have to go off line and must be treated as read only.
Hilary Cotter
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
"combfilter" <asdf@.adsf.com> wrote in message
news:MPG.1cff9d563dc5267e989698@.news.newsreader.co m...
> In article <eU3NT3YYFHA.3584@.TK2MSFTNGP12.phx.gbl>,
> hilary.cotter@.gmail.com says...
> so do i set it up just under the configure replication... in enterprise
> manager? is there anything special i need to do? Is there a smarter
> way to move tables from one db to another continually?
> Thanks,
> -comb
|||In article <eBEXevgYFHA.1796@.TK2MSFTNGP15.phx.gbl>,
hilary.cotter@.gmail.com says...
> Yes, and what do you mean by move tables continuously? For this possibly log
> shipping is the best as it will mirror objects with no intervention, but
> your destination will have to go off line and must be treated as read only.
They are historical tables that are updated throughout the day. See the
db has about 750 tables in it, I am only needing to replicate about 4 of
them. That is why I 86'd the idea of logshipping. I thought with log
shipping it was an all or nothign type deal? Like the entire db or
nothing at all.
Thanks for any advice.
comb

Publisher cannot be droped becaused Remote Distributor down

Hi all,
I am having a problem now. I cannot drop my publisher and publication because i was uninstalled the remote distibutor before i disable al lthe publication. Now the remote distibutor no longer exist.
Can another one help me? Urgent!!I don't know of any way to remove replication using the GUI tools in the situation you've described, but it can be done fairly easily using Transact SQL stored procedure calls. Check out sp_droppublication (http://msdn.microsoft.com/library/en-us/tsqlref/ts_sp_repl2_617y.asp) and pay special attention to the @.ignore_distributor parameter. Microsoft normlly recommends that you use this only with the help of their PSS group, but your data may not be worth $750 to open a support incident with them, so you may choose to "go it alone" instead of calling them for help.

-PatP

Publication has expired

I have setup transaction replication using seperate server for distribution
box.
Server A - Publisher (Win2003, SQL2000 SP818)
Server B - Distributor (Win2003, SQL2000 SP818)
Server C - Subscriber1 (Win2003 and SQL2000 SP818)
Server D - Subscriber2 (Win2003 and SQL2000 SP818)
Server E - Subscriber3 (Win2000, SQL2000 SP818)
Server A has 3 publishers and each publisher has more than 10 articles, one
of them we use it for monitoring replication by update a datetime column from
sql job.
The trans. replication are running fine execpt the subscriber3. This
subsciber always get sthe subscription expires errors, but the monitor
article does get updated. And the wired thing is the replication monitor on
the distribution server shows that the agent is in suspect and no reponse
within 10 min after each snapshot/initation.
I did query the MSDistribution_History and there is only one row which the
date I ran the snspshot. All the retention and history period are default.
Does anyone knows that it is Win2003 to Win2000 issue or something else.
Thanks in advance
This guy expired prematurely because your history retention is less than
your publication retention. Bump this setting up to your publication
retention, and be highly proactive about sensing when this guy has dropped
off the network for more than 1 day.
Hilary Cotter
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
"kc" <kc@.discussions.microsoft.com> wrote in message
news:7B0A51D7-F9BD-4281-A7F3-E8144164F02A@.microsoft.com...
> I have setup transaction replication using seperate server for
distribution
> box.
> Server A - Publisher (Win2003, SQL2000 SP818)
> Server B - Distributor (Win2003, SQL2000 SP818)
> Server C - Subscriber1 (Win2003 and SQL2000 SP818)
> Server D - Subscriber2 (Win2003 and SQL2000 SP818)
> Server E - Subscriber3 (Win2000, SQL2000 SP818)
> Server A has 3 publishers and each publisher has more than 10 articles,
one
> of them we use it for monitoring replication by update a datetime column
from
> sql job.
> The trans. replication are running fine execpt the subscriber3. This
> subsciber always get sthe subscription expires errors, but the monitor
> article does get updated. And the wired thing is the replication monitor
on
> the distribution server shows that the agent is in suspect and no reponse
> within 10 min after each snapshot/initation.
> I did query the MSDistribution_History and there is only one row which the
> date I ran the snspshot. All the retention and history period are
default.
> Does anyone knows that it is Win2003 to Win2000 issue or something else.
> Thanks in advance
|||In my case, the monitor article in the subscriber had same time as the
publisher when it was mark for expiration. Therefore it is not a network
issue.
By default, the hsitory rentention is 48 hrs and transaction rentention is
72 hrs, so I don't understand what do you mean that I need to bump the
setting up?
Thanks
KC
"Hilary Cotter" wrote:

> This guy expired prematurely because your history retention is less than
> your publication retention. Bump this setting up to your publication
> retention, and be highly proactive about sensing when this guy has dropped
> off the network for more than 1 day.
> --
> Hilary Cotter
> 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
> "kc" <kc@.discussions.microsoft.com> wrote in message
> news:7B0A51D7-F9BD-4281-A7F3-E8144164F02A@.microsoft.com...
> distribution
> one
> from
> on
> default.
>
>