web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

AX 2012 R3: Merging Databases into one database

(0) ShareShare
ReportReport
Posted on by 725

Hi All,

We are an organization having offices in different parts of the world. Currently, we have

office in UK, USA, South Africa, UAE and in India. Each location is having independent AX setup, With the change in strategy

, management needs all these database to be merged into one location with one single database. My query is we can bring in

one location db as a simple restore but after that we use data migration frame work or write a small utility to migrate

the data from other locations into this db, Now the question is for the Shared Table data, how do we manage that?

I am sure this challenge would have been faced by many, Appreciate all your help. A big Thankyou in advance

 

*This post is locked for comments

I have the same question (0)
  • Brandon Wiese Profile Picture
    17,788 on at

    I doubt very much "many" companies have done what you are suggesting.

    The shared table problem is a serious one.  Obviously you have to identify and resolve all conflicts in those tables before any merge can be considered.

    The RecId problem is far more serious.  It goes without saying that the different databases will collide on RecId in virtually every table.

  • Sohaib Cheema Profile Picture
    49,438 User Group Leader on at

    Does your organization has a good communication channel, after DB will be merged at one place and all users from everywhere will be using ERP connected to one DB.

    For few entities data is already shared/company-less e.g. Purchase Requisitions don’t bother DataAreaId.

    Another point which has been specified above as well, are those tables, which are using foreign key RefRecId relationships. Seems we have to do manual work in these cases.

  • Syed Zeeshan Haider Jafry Profile Picture
    725 on at

    Is there any tool to do that? in AX 2009 it was simple using dat files. in AX 2012 i have thought about creating partition and then write script to copy the data, but drawback of that is we will not have all companies listed in single client access file.

  • Brandon Wiese Profile Picture
    17,788 on at

    I don't think it was nearly as simple in earlier versions of AX as you claim.  You still had RecId issues, and records that pointed to other records by their RecId.  The migration from 3.0 to 4.0 renumbered all of the RecId's in every table, and it was a complex process.

    In any case, in 2012 you have quite a bit more sharing and "company-less" tables than you had before.

    There are so many questions.  Are the companies going to share the same chart of accounts, or will they have their own chart of accounts?  You'll have to have a merged set of products.  Is there any overlap between the database in products or released products?  The list just goes on, and on, and on.

  • Syed Zeeshan Haider Jafry Profile Picture
    725 on at

    I know the list that needs to be considered is big, and may miss few when we would be actually doing it.

    chart of account would be different. but dimensions needs to be shared, and dimension combination table would be a nightmare then. Product number would also be different, but that would require to be reviewed as we would require to have a common catalog.

    Global address book tables would be challenging. Workers we can manage.

    whats the best way to deal this? any other plan that we can consider?

    Connectivity is not an issue.

  • Brandon Wiese Profile Picture
    17,788 on at

    Sure, I can think of other plans.

    First, why do the databases need to be merged into a single database?

  • Syed Zeeshan Haider Jafry Profile Picture
    725 on at

    Organization is planning to move to cloud, reducing the hardware cost. Plus consolidation would be easier.  Manage AX at one place instead of 5 different locations.

  • Brandon Wiese Profile Picture
    17,788 on at

    You could still have 5 databases in the cloud.  It probably wouldn't change the cost much either.  Are there other reasons?

  • Brandon Wiese Profile Picture
    17,788 on at

    How would consolidation be easier?  Financial reporting?   How is that being done now?

  • Syed Zeeshan Haider Jafry Profile Picture
    725 on at

    by consolidation, i mean, analyzing different locations data  in one report. Currently we are bringing DB backup in one server and querying it. i know we can do this using SSIS but we have not used it until.

    So you are suggesting keeping all DB separate with separate AOS'es?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans