Replication setup on Dataware house application

  • I am thinking of setting up a transaction replication on the server. We have dataware house kind of application and need to distribute data to client every week. Right now there is VB application which is taking care of distributing data to client. I wanted to get rid of that and try to use Transaction Replication.

    Question.

    1. Which replication type should I use. ( Data gets populated in a batch, means 50,000 records gets populated in the table from text file in one time.)

    2. Should I give subscriber the right to pull data from publishers or should I push the data.

    3. should I use distributor server as a separate server.

    4. What should i don if publishers fails.

    5. Is there a good article for describing issues.

    any help will be appreciated.

  • You have a lot more to look at before you will be able to make a decision, but my first impression is that transactional replication is probably not going to be the best solution for you.

    Transactional replication sends one record at a time. This behavior can be changed somewhat with some configuration, but basically, if you bulk load 50,000 records into your publisher, replication will sent 50,000 insert statements to each subscriber. If you are bulk-loading on a weekly basis, this seems like the wrong technology choice.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply