Post reply

Which one is better for Production

  • October 9, 2009 at 10:29 am

    #205437

    Hi

    Can any one tell which one is better in production

    1)Log shipping

    2)Replication

    3)Mirroring

    4)Clustering

    My production server in one min there will more tthan one lack of records on insertion and updation and some deletion will happen it is 24/7 suport.

    which one can i choose, i am using Ms sql 2005

    If u know any link related it would be helpful

    Thanks in Advance

    Parthi

    Thanks
    Parthi

  • October 9, 2009 at 10:31 am

    #1064232

    parthi-783546 (10/9/2009)

    Hi

    Can any one tell which one is better in production

    1)Log shipping

    2)Replication

    3)Mirroring

    4)Clustering

    Depends

    What are you trying to achieve?

    What's your budget?

    What's your downtime SLA?

    All 4 (and a few others) have their place. There's no one that's better than all the others.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • October 9, 2009 at 10:48 am

    #1064242

    I need to Satisfy the customers need with less amount of data lose.

    In the event of a corruption, or other disaster, the maximum amount of data loss is the last 15 minutes of transactions.

    so and so...

    Thanks
    Parthi

  • October 9, 2009 at 10:58 am

    #1064248

    I think log shipping is a cheaper of all those options and efficient as you can do log backups every 15 minutes or so and a weekly full database backup. You can easily setup jobs to handle this and also have a file server where to keep an additional copy of the log file backups and the full backups. This would allow point in time recovery and you could log ship this data to the data warehouse for analysis, reporting, etc.

    Thanks,

    S

    --
    :hehe:

  • October 9, 2009 at 11:02 am

    #1064250

    I would go for database mirroring, it is easy to setup and will provide a fail-over partner in the event that the primary database becomes unavaiable.

    Also it has the advantage over log-shipping, in that it provides automatic failover when used with a witness server.

    Aside from mirroring, I would ensure that you have a robust back-up / restore strategy in place and run CheckDb often.

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

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