CYBER MONDAY ALL MONTH. Save 25% on your first month or full year!*
*Through December 2nd. Applies to first charge of a new subscription only. View Plans
LIMITED-TIME OFFER: Save 25% on
any subscription through December 2nd!*
Our Cyber Monday promo is here early, and it's staying all month long!
*Applies to first charge of a new subscription only.
Do more with
Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
pull is for subscriber location in DR site, far aways from publisher and distributor .
do you agree that ?
why is it? any good thing if architecture in this way ?
what if it is not in the same network, e.g. a subscriber in DR site. another subscribers on local LAN, e.g. just upstairs , what should I do then ?
you mean distributor always the busiest one ?
you said: 'push subscriptions runs the Distribution Agent on the Publisher', so it should be the publisher busy but not distributor, right?
hi, but people might not know this diff. right? hard to know
this seems to me that we don't need distributor at all, as the agent only in publisher or subscriber, distributor is not in this picture
so this means if we have more and more subscribers, pull is better as the distributor agent on subscriber, we don't want all distributor agent all on publisher as it will be high loading for publisher.
it is just about distribution of load instead of it is subscriber far ways or short distance, right?
on distributor itself only ? as publisher should only push once but distributor has to coordinate the rest of data transfer ?
I heard there are no caculation for this but as per replication setup , 32GB additional of RAM need to add to that box, agree?
then we go back to the same conclusion, when there are lot of subscribers, we should use as distributor agent will be on subscriber.
is this means we decide pull or push based on the existing hardware we have ?
subscribers or publisher you are talking about ?
so for an additional replication added, no need to add more RAM and tempdb .ndf file ?
so any monitoring metric for me to ping pong that out ? I can make use of the the monitoring tools
what the performance monitor giving us is we have to check it out MANUALLY and it can be a big trouble if we can't start to see there are problem/potential problem before something even bigger happen.
you mean you just use these ?
I don't see I can give you specific point, how?
IT issues often require a personalized solution. With Ask the Experts™, submit your questions to our certified professionals and receive unlimited, customized solutions that work for you.
Start 7-Day Free Trial
Start 7-Day Free Trial