push or pull - SQL 2000 Transactional

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

BATMAN - 27 Oct 2006 23:50 GMT

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!

Reply to this Message

BATMAN - 28 Oct 2006 00:56 GMT

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

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

Reply to this Message

Hilary Cotter - 28 Oct 2006 01:01 GMT

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.

Signature

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

>I know it is recommended for topologies with many subscibers... We have
>only
[quoted text clipped - 9 lines]
>>
>> Thanks!

Reply to this Message

BATMAN - 28 Oct 2006 04:16 GMT

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

Thanks Hilary!

> 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
[quoted text clipped - 13 lines]
> >>
> >> Thanks!

Reply to this Message

Hilary Cotter - 28 Oct 2006 12:47 GMT

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.

Signature

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

> So we are using a remote distributor with a few subscibers, 4 to be
> exact...
[quoted text clipped - 21 lines]
>> >>
>> >> Thanks!

Reply to this Message

BATMAN - 28 Oct 2006 18:54 GMT

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

> 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
[quoted text clipped - 30 lines]
> >> >>
> >> >> Thanks!

Reply to this Message