Post reply

Design considerations for Replication

  • January 23, 2008 at 12:02 am

    #185837

    Need help in design considerations for Replication.

    Thanks

  • January 23, 2008 at 12:10 am

    #770759

    Hi

    Search this forum and the web for various articles and read them. Check out BOL. Come back with some specific doubts. 🙂

    "Keep Trying"

  • January 23, 2008 at 1:53 am

    #770779

    I guess I was so time pressed to get the answer that I didnt frame the question well. I have a database which will be set for replication later. I wanted to know the database/table design considerations so that the replication doesnt break.

    Thanks.

  • January 23, 2008 at 2:06 am

    #770785

    Your design will differ from environment to environment. You have to look at your variables like line speeds, database sizes, other servers on same network and who will access the database.

    Have a look at this article as is it will give you a better idea of what you need to take into consideration.

    http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1271920,00.html

  • January 24, 2008 at 12:51 am

    #771165

    Hi,

    I don't think you have that much to be concerned with when it comes to design.

    There are a few rules that apply to replication...such as some datatypes cannot be replicated (if I remember correctly)

    What you need to think about, IMHO, is what you want to do with the data...I few questions I would ask myself might be

    How much data will you want to distribute?

    How frequently will the data need to be updated?

    Will the data need to be updated at the subscribing end?

    ..to name but a few

    Answering these questions will help you decide what type of replication to use and therefore what you need to consider in the design i.e. Identities, Primary Keys.

    Your question was quite broad 🙂

    HTH

    Graeme

Viewing 5 posts - 1 through 4 (of 4 total)

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