Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Data replication option with NAV 2009
sil21
Member Posts: 55
We have a client with 2 locations running NAV 2009 RTC. The two locations run as one company in NAV, and do a lot of inventory transfers back and forth. One location is remote, and in a very rural area with undependable internet access. This location does most NAV functions; purchase order entry and receiving are mission critical at this location. We are faced with 2 issues - the speed is slow on a regular basis, and we face the potential of the connection going completely down on an occassional basis.
The hardware folks would like to have a separate app and db server at remote location which then recplicates with the main database server's data. (I'm not sure if this is officially clustering....which I know is not supported). With this configuration, the remote location could run without any connectivity, and the performance would be as good as local performance. The bandwidth would be used only for data replication.
Has anyone done anythning like this before ?
We have proposed a emergency local copy of nav for when the connection is down, and this would only run the mission critical operation. We would then write some code to port the new purchases and receipts to the main system when the connection is back. Not too flashy ... and does not solve their speed issues ....
The hardware folks would like to have a separate app and db server at remote location which then recplicates with the main database server's data. (I'm not sure if this is officially clustering....which I know is not supported). With this configuration, the remote location could run without any connectivity, and the performance would be as good as local performance. The bandwidth would be used only for data replication.
Has anyone done anythning like this before ?
We have proposed a emergency local copy of nav for when the connection is down, and this would only run the mission critical operation. We would then write some code to port the new purchases and receipts to the main system when the connection is back. Not too flashy ... and does not solve their speed issues ....
0
Comments
The only issue is that It's Retail solution so separating replication object from Retail will be an issue.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
is a very good solution and it works like LS retail replicator, without the pain to buy the entire LS retail solution!
Check out my NAV blog http://opennav.wordpress.com/