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)

Synchronization taking more time after the model store move

(0) ShareShare
ReportReport
Posted on by 3

Hi,

I did the model store move on production from stage. After model store move, i open the AX client and started the db synchronization. It is taking more than 2 hours.

Could you please explain me that what may be the problem and how to solve this issue?

Thanks,

Hari

*This post is locked for comments

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    300,917 Super User 2025 Season 2 on at

    Hi Hari,

    It can be caused by many things. Are there more users in the system? Is there regular maintenance on the database, e.g. rebuild/reorganize indexes? You can do monitoring on hardware resources to see if there is any bottleneck.

  • Hariharans87 Profile Picture
    3 on at

    Hi Andre,

    Thanks for your reply. Yes, 300 users are there. In SQL, reorganize index job is scheduled daily basis and running. Any idea?

    Hari

  • Verified answer
    André Arnaud de Calavon Profile Picture
    300,917 Super User 2025 Season 2 on at

    Hi Hari,

    You need to do monitoring on e.g. hardware resources, SQL indicators. Then you can find out what could be your  bottleneck.

    Maybe insufficient memory. When you have virtualized environments, also check if there is overcommitment of cpu's.

  • Verified answer
    Community Member Profile Picture
    on at

    A list of things could cause slow performance while synchronize. What Ax does is altering your data dictionary in SQL, and that can cause indexes to be rebuild. There are a lot of things that I would ask myself like:

    - did I change a lot in the data dictionary in the new modelstore? If so a lot has to be synchronized.

    - did I change any settings in SQLadministration like compression settings/ fill factor etc. These will cause index rebuilds on all effected tables.

    - does SQL server have enough memory to perform this task in its machine?

    - is SQL server limited in use of CPU and/or memory?

    - are the databases of your sql on separate disks, and are those fast?

    - when synchronizing am I the only user in the system? else sql has to wait till other requests are handled.

    - if virtualized is the hardware set to work in 'Balanced mode'/ 'Energy mode' / 'Green Mode' or how manufactures call it nowadays. It is good for environment and slow people because it slows performance by 30%.

    - if virtualized did I assign more CPU Cores than I physically have? If so overcommitting will slow down your system.

    - do the file in SQL have free space before I start adding tables/columns etc. or do they have to grow? If growth is set to grow 1 mb every time it takes a while on slow disks. Grow it before autogrowth kicks in.

  • Hariharans87 Profile Picture
    3 on at

    Thanks Gentlemen. I will look into the this.

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