Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 309
  • Last Modified:

SQL 2008 transactional replication

I'm new to transactional replication. Server A is a production database. Server B is the server that I want to have the subscribers on. I do not want to do anything that will cause performance issues to server A.  I only have 2 servers adn I will not be monitoring. I know I put the Publisher on A and the subscriber on B but can I put the Distributer on B as well? And then to I put the distribution agent on B as well OR should I put the Dristributer on A and then run each agent at the subscriber (pull)??? What is the best practice?
0
cheryl9063
Asked:
cheryl9063
1 Solution
 
TempDBACommented:
Generally distributor is never kept at the subscriber end as if subscriber goes down, then you need to resetup the publication. Else just re-initializing the subscription will do. Apart from that, the best practise is to keep it on another server.
                   In your situation, I will suggest keeping the distributor on publisher end and creating pull subscriptions. This shouldn't make much performance impact but there should be some kind of monitoring for the replication else if there is some problem and commands are not flowing, the dtabase size will blow up.
0
 
jjjosefCommented:
I think the publisher doesn’t care about the exact location of the database files of  subscriber
for more information go through the below article

http://www.sql-server-performance.com/2010/transactional-replication-2008-r2/
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now