Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 300 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 35 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
Database replication/merge
downsouth
Member Posts: 2
Hi Y'all,
I would enormously appreciate help with the following Axapta 3.0 setup. I would like to merge an Axapta 3.0 database complete with settings and data as well as record ID's to another database in the same SQL 2005 instance. I am aware that Axapta 4.0 has made the problem easier to cope with but I cannot at this point upgrade.
My understanding thus far of the record ID's is that they are assigned on the inital database, sequentially, without checking for available (free) ID's, to compound the problem ID's are controlled Globally ,not per table, which could result in duplicate records or missing(dropped) records in the replicated database.
The solution in my opinion would be to create a table on the replicated/merged database that would monitor/synchronise the records on both the databases, or have the replication "filter" through a custom process.
The merge will be once off and exist thereafter only in the new location, my research thus far has recommended a snapshot merge.
Please post a pedantic step for step guide if you are aware of a solution.
Thanks in advance,
Downsouth
I would enormously appreciate help with the following Axapta 3.0 setup. I would like to merge an Axapta 3.0 database complete with settings and data as well as record ID's to another database in the same SQL 2005 instance. I am aware that Axapta 4.0 has made the problem easier to cope with but I cannot at this point upgrade.
My understanding thus far of the record ID's is that they are assigned on the inital database, sequentially, without checking for available (free) ID's, to compound the problem ID's are controlled Globally ,not per table, which could result in duplicate records or missing(dropped) records in the replicated database.
The solution in my opinion would be to create a table on the replicated/merged database that would monitor/synchronise the records on both the databases, or have the replication "filter" through a custom process.
The merge will be once off and exist thereafter only in the new location, my research thus far has recommended a snapshot merge.
Please post a pedantic step for step guide if you are aware of a solution.
Thanks in advance,
Downsouth
0