Replicating Navision in two locations

theant

Hi,

We have an office in London and an office in Brighton and we need to use Navision in both places. I have looked into using TS but I am also considering having a server in both sites and using transactional replication. This would give me the advantage of all users connecting to a local server and give me an up to data backup in case one server failed.

Is this a good idea or am I barking up the wrong tree?
Does anyone have experience of this scenario?
Does the fear of data conflict make this solution unfeasible?


I would be very grateful for any information you could give me.

Ant

ara3n

Please look at LS Retail. If you want replication and local Navision server.

The amount of money and time it will require to setup two separate servers will send you back to terminal services as a solution.


Navision was not build to be a connectionless ERP. Standard SQL replication will not work. Unless The two offices are two companies in Navision, in that case you can have separate servers. and you can setup one way replication for each company.

Miklos_Hollender

Probably Landsteinar DataDirector is the best product for this stuff (they also have a basic Scheduler but forget that), but it's not very easy to set up correctly. You need deep understanding of what tables are being used at what places and so on.

Basically, it's recommended for those directions where different sites use mostly different kind of functionality. A good example is a retail store, when only Item-related master data need to do come down from the HQ and only POS transactions need to go up to the HQ and be posted there. That's OK. This is the scenario it was originally intended for. Basically, it's a "only what's changed" type of sync from the HQ to the store, and an "only the new entry numbers" type of sunc from the store to the HQ. Things more complicated than this scenario, such as entering orders at one site and shipping them at another site might be very hard to configure.

Therefore, I'd rather recommend Citrix, Jetro (it is said to be cheaper Citrix, I don't know it), or TS if the budget is too tight.

Note that there are many Citrix-related fixes in SP3 so it seems many folks do it this way and MS started to pay attention to it, it seems.

ara3n

what kind of fixes did they fix for citrix? I didn't see it in document for sp3.