Post reply

synchronize remote database

  • August 19, 2009 at 1:32 am

    #132789

    I have a situation where in I have synchronize the secondary server with the primary server having 20GB database, and both are in distinct locations physically

    (Log shipping and Transactional replication are not applicable to this situation)

    is there any tool or approach to solve this...

    thank you in advance

    Thanks ,

    Shekhar

  • August 20, 2009 at 8:42 am

    #1042165

    You have to ....

    1) synchronize the actual data between two databases on different servers? i.e. merge or some type replication??

    2) or you just need a copy of one database on another server that will stay up to date? i.e. log shipping??

    Sorry, just trying to understand the question.

  • August 20, 2009 at 9:53 am

    #1042233

    ShekharNaidu (8/19/2009)

    (Log shipping and Transactional replication are not applicable to this situation)

    What is the constraint you have when u say you cannot implement log shipping on this situation?


    Pradeep Singh

  • August 20, 2009 at 9:59 am

    #1042236

    I read some where that to implement Logshipping/Trasactional replication we need to start the 2 SQL Server services with same domain account...

    as my systems are remotely distributed I cannot fullfil this requirement..

    now I am confused after reading the below article

    http://support.microsoft.com/kb/321822#appliesto

    Thanks ,

    Shekhar

  • August 20, 2009 at 10:03 am

    #1042241

    You dont need to have same account!!

    Account used on primary should have write access to the shared folder, where as the account used by secondary should have read permission on the file share where log backups will be stored. You can also setup cross domain log shipping by having trusted domains.

    See these links :

    http://support.microsoft.com/kb/321247%5B/url%5D

    http://www.sqlservercentral.com/Forums/Topic654543-357-1.aspx%5B/url%5D


    Pradeep Singh

  • August 20, 2009 at 10:10 am

    #1042245

    LogShipping is the option you should follow, it doesnt matter what the service accounts are.

    you Just take care to see that your logs are not heafty in full recovery mode. (Check bulk-logged as an option.. but it should be your call, if you are ok with some data loss else FULL mode.)

    Maninder
    www.dbanation.com

  • August 20, 2009 at 10:18 am

    #1042255

    Mani Singh (8/20/2009)

    you Just take care to see that your logs are not heafty in full recovery mode. (Check bulk-logged as an option.. but it should be your call, if you are ok with some data loss else FULL mode.)

    In bulk recovery model, the Log file itself grows lightly where as the log backup contains all changed extents by the bulk logged operation and hence the size of the log backup in bulk logged mode will not be less.


    Pradeep Singh

  • August 20, 2009 at 10:44 pm

    #1042598

    as I said the servers are spread over the internet.. we cannpt have shared locations.. between them..

    Thanks ,

    Shekhar

  • August 24, 2009 at 10:21 pm

    #1043977

    I have tried transactional replication.. (with push subscription)

    but it is tooooo long time to replicate the intial subscription..

    it is replicationg 1 lack rows for 5mins... where as I have lacks and even crores of rows in my tables..

    thought this is might help you ... for more suggestions..

    Thanks ,

    Shekhar

Viewing 9 posts - 1 through 8 (of 8 total)

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