Database infrustructure

  • I've just joined a company and they have this plan to revamp their site..

    They want to separate their data writes from the reads..

    The web/app servers would hit one server to write data and another to read data.

    The writerSQLServer would then do transactional replication to the ReadSQLServer.

    Their main concern is being able to grow as needed, with this model, they say they can keep adding reads/writes servers as needed.

    My concern is the impact on an application having to read/write from two different servers and once we start adding we will have to start using merge? replication.

    Any thoughts?

  • I have a simple math solution for you :

    2 servers = 2 times the costs

    2 servers also means that the data has to be written twice instead of one which makes no sens unless you have a very special situation I've never heard of.

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

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