Home > Archive > MS SQL Server Replication > October 2006 > push or pull - SQL 2000 Transactional









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author push or pull - SQL 2000 Transactional
BATMAN

2006-10-28, 7:22 pm

I just talked to Microsoft and I was told to do push subscriptions instead of
pull, to run the distribution agents on the distributor. I have come across
different resources that say otherwise... What is the best approach with a
distributed topology.

Thanks!
BATMAN

2006-10-28, 7:22 pm

I know it is recommended for topologies with many subscibers... We have only
a few, few reporting servers...

"BATMAN" wrote:

> I just talked to Microsoft and I was told to do push subscriptions instead of
> pull, to run the distribution agents on the distributor. I have come across
> different resources that say otherwise... What is the best approach with a
> distributed topology.
>
> Thanks!

Hilary Cotter

2006-10-28, 7:22 pm

For high load you should use a remote distributor. For large numbers of
subscribers use pull. I am not sure why they have made these recommendations
but they were probably not made lightly.

--
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

"BATMAN" <BATMAN@discussions.microsoft.com> wrote in message
news:E6E6ABEE-7C4D-434E-A6D5- 015B7892BD90@microso
ft.com...[color=darkred]
>I know it is recommended for topologies with many subscibers... We have
>only
> a few, few reporting servers...
>
> "BATMAN" wrote:
>


BATMAN

2006-10-28, 7:22 pm

So we are using a remote distributor with a few subscibers, 4 to be exact...
So should we use push subscriptions?

Thanks Hilary!

"Hilary Cotter" wrote:

> For high load you should use a remote distributor. For large numbers of
> subscribers use pull. I am not sure why they have made these recommendations
> but they were probably not made lightly.
>
> --
> 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
>
> "BATMAN" <BATMAN@discussions.microsoft.com> wrote in message
> news:E6E6ABEE-7C4D-434E-A6D5- 015B7892BD90@microso
ft.com...
>
>
>

Hilary Cotter

2006-10-28, 7:22 pm

What sort of load will you be experiencing? Do you know how much CPU your
load will create on your server? If it is substantial go to remote
immediately, if not you can use a local distributor. For this small number
of subscribers I would always use push, unless they are frequently
disconnected.

If you are using a remote distributor you must make sure it is clustered,
otherwise you are asking for trouble as you have a single point of failure.

--
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



"BATMAN" <BATMAN@discussions.microsoft.com> wrote in message
news:14FDB883-2651-469C-A006- A2324656DDA7@microso
ft.com...[color=darkred]
> So we are using a remote distributor with a few subscibers, 4 to be
> exact...
> So should we use push subscriptions?
>
> Thanks Hilary!
>
> "Hilary Cotter" wrote:
>


BATMAN

2006-10-31, 12:24 am

Our load is 1million+ transactions a day...

We do currently have a clustered remote distributor...

And we have 4 subscribers (server subscribers) that will never be
disconnected, unless of outage.

So with that said, is push the best way to go and why?

Thanks!

Michael


"Hilary Cotter" wrote:

> What sort of load will you be experiencing? Do you know how much CPU your
> load will create on your server? If it is substantial go to remote
> immediately, if not you can use a local distributor. For this small number
> of subscribers I would always use push, unless they are frequently
> disconnected.
>
> If you are using a remote distributor you must make sure it is clustered,
> otherwise you are asking for trouble as you have a single point of failure.
>
> --
> 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
>
>
>
> "BATMAN" <BATMAN@discussions.microsoft.com> wrote in message
> news:14FDB883-2651-469C-A006- A2324656DDA7@microso
ft.com...
>
>
>

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com