Hi,
We have a distribution server that have all of our
transactional replications on it. All the distribution
agents and log reader agents keep time out and we have to
keep restart the agents.
What's the roob cause of this? Too many replications on
one distribution box? Or too many agents running at the
same time schedule?
Many thanks.
JJDon't the distribution agents keep trying for a certain number of times
before they error out? While they keep trying, you don't need to manually
restart them.
Distribution agents often times out in our environment. Causes I have found
are:
1. Blocking on the subscriber;
2. No more space on the subscriber database;
3. Server connection problem;
Richard
"JJ Wang" <jwang@.leapwireless.com> wrote in message
news:01a501c39284$479d5ee0$a401280a@.phx.gbl...
> Hi,
> We have a distribution server that have all of our
> transactional replications on it. All the distribution
> agents and log reader agents keep time out and we have to
> keep restart the agents.
> What's the roob cause of this? Too many replications on
> one distribution box? Or too many agents running at the
> same time schedule?
> Many thanks.
> JJ
Showing posts with label replications. Show all posts
Showing posts with label replications. Show all posts
Monday, March 26, 2012
Friday, March 23, 2012
Replication between SQL 2000 & SQL 2005
We currently replicate two databases. We would like to installed SQL 2005 o
n
the publisher of these replications. The subscribers will still be on
SQL2000. Will this work? What potential problems should I look for?
ThanksI built a couple of test servers to test upgrading from SQL Server 2000 to
2005. One of the components that I tested was replication.
I think that I upgraded the publisher first, but I cannot remember for sure.
I ended up upgrading both servers. Replication worked when I had one box on
2000 and one on 2005 and it worked after upgrading the other box to 2005.
I don't think that you are in for any surprises.
Keith Kratochvil
"Lynnie" <Lynnie@.discussions.microsoft.com> wrote in message
news:9ED90D1A-0EDF-4B3F-9E36-4792DD052F9B@.microsoft.com...
> We currently replicate two databases. We would like to installed SQL 2005
> on
> the publisher of these replications. The subscribers will still be on
> SQL2000. Will this work? What potential problems should I look for?
> Thankssql
n
the publisher of these replications. The subscribers will still be on
SQL2000. Will this work? What potential problems should I look for?
ThanksI built a couple of test servers to test upgrading from SQL Server 2000 to
2005. One of the components that I tested was replication.
I think that I upgraded the publisher first, but I cannot remember for sure.
I ended up upgrading both servers. Replication worked when I had one box on
2000 and one on 2005 and it worked after upgrading the other box to 2005.
I don't think that you are in for any surprises.
Keith Kratochvil
"Lynnie" <Lynnie@.discussions.microsoft.com> wrote in message
news:9ED90D1A-0EDF-4B3F-9E36-4792DD052F9B@.microsoft.com...
> We currently replicate two databases. We would like to installed SQL 2005
> on
> the publisher of these replications. The subscribers will still be on
> SQL2000. Will this work? What potential problems should I look for?
> Thankssql
Labels:
database,
databases,
installed,
microsoft,
mysql,
onthe,
oracle,
publisher,
replicate,
replication,
replications,
server,
sql,
subscribers
Replication between SQL 2000 & SQL 2005
We currently replicate two databases. We would like to installed SQL 2005 on
the publisher of these replications. The subscribers will still be on
SQL2000. Will this work? What potential problems should I look for?
ThanksI built a couple of test servers to test upgrading from SQL Server 2000 to
2005. One of the components that I tested was replication.
I think that I upgraded the publisher first, but I cannot remember for sure.
I ended up upgrading both servers. Replication worked when I had one box on
2000 and one on 2005 and it worked after upgrading the other box to 2005.
I don't think that you are in for any surprises.
--
Keith Kratochvil
"Lynnie" <Lynnie@.discussions.microsoft.com> wrote in message
news:9ED90D1A-0EDF-4B3F-9E36-4792DD052F9B@.microsoft.com...
> We currently replicate two databases. We would like to installed SQL 2005
> on
> the publisher of these replications. The subscribers will still be on
> SQL2000. Will this work? What potential problems should I look for?
> Thanks
the publisher of these replications. The subscribers will still be on
SQL2000. Will this work? What potential problems should I look for?
ThanksI built a couple of test servers to test upgrading from SQL Server 2000 to
2005. One of the components that I tested was replication.
I think that I upgraded the publisher first, but I cannot remember for sure.
I ended up upgrading both servers. Replication worked when I had one box on
2000 and one on 2005 and it worked after upgrading the other box to 2005.
I don't think that you are in for any surprises.
--
Keith Kratochvil
"Lynnie" <Lynnie@.discussions.microsoft.com> wrote in message
news:9ED90D1A-0EDF-4B3F-9E36-4792DD052F9B@.microsoft.com...
> We currently replicate two databases. We would like to installed SQL 2005
> on
> the publisher of these replications. The subscribers will still be on
> SQL2000. Will this work? What potential problems should I look for?
> Thanks
Labels:
database,
databases,
installed,
microsoft,
mysql,
oracle,
publisher,
replicate,
replication,
replications,
server,
sql,
subscribers
Subscribe to:
Posts (Atom)