Replication NAV DB with SQL 2005 Server Management Studio

defiant701
defiant701 Member Posts: 79
edited 2006-08-29 in NAV/Navision Classic Client
Hi there

I have a question belonging replication procedures with Navision through SQL 2005. Currently we are using several localized NAV 4.0 SP2 Versions that are located at our HQ. Almost every subsidiary is able to work on terminal servers all around the globe(all? not really only Greece is offering resistence [-( with their latency). So we want to start bulding and setup the new db in our HQ and make a snapshot replication for Greece GR. After that GR will become publisher and some transactional replication should update the HQ db. So my question is: Is it possible that way and does it also work the other way round if we to make some changes in the db in the HQ?
Hope you understand what I wanted to post...
Debuggers don't remove bugs, they only show them in slow-motion

LinkedIn
XING

Comments

  • nunomaia
    nunomaia Member Posts: 1,153
    Replication in SQL Server

    Snapshot – use this replication if the subscriber can have data out of date
    Transactional Replication – use this if You want the changes to be propagated to subscriber as they occur
    Merge Replication - subscriber might update the same data at various times and propagate to the Publisher

    To use data in HQ as read only you can use Snapshot or Transactional Replication. If you use Merge Replication with NAV, will lead data conflicts and consequently data corruption.

    My advice to you, is to use in the HQ as readonly.
    Nuno Maia

    Freelance Dynamics AX
    Blog : http://axnmaia.wordpress.com/
  • defiant701
    defiant701 Member Posts: 79
    Thanks for your advice. I'll try it a post a feedback when done (and functional).

    Regards
    Debuggers don't remove bugs, they only show them in slow-motion

    LinkedIn
    XING
  • Scott_Frappier
    Scott_Frappier Member Posts: 90
    Remember:

    With replication, you will limit how many schema changes can occur within the database. We have a client that is using merge replication, and that type of replication limits schema changes (you cannot add a key, change fields, et cetera without dropping the article and then re-publishing the data).

    If you are doing this for reporting capabilities, you may want to consider log shipping. This allows you to have multiple databases on one server, and then you can create queries to import the data into the HQ database. The Log-shipped databases are readonly, so you cannot update them, but they are great for reporting/data integrations.

    Also, with SQL Server 2005 you now have the capability of using Database Mirroring technology...that may be something that you could explore as well.
    Scott Frappier
    Vice President, Deployment Operations

    Symbiant Technologies, Inc.
    http://www.symbiantsolutions.com

Categories