dynamics 365 on premises slow - how to rebuild indexes

(0) Share

Report

Posted on by Community Member

Hi , need ideas how to improve performances of dynamics 365 on premises. we have crm database is about 82 GB in size and performing very slow. I have cleared most of cancelled / succeeded system jobs . Can we rebuild indexes to improve performances ? any advice would be great ...

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

ashlega 34,477 on at

Like (0)

Report

Hi,

if you just wanted to rebuild the indexes (and it might or might not help with the performance), you wouldn't be able to do it from CRM, but, I guess, you might go to the SQL server and run the kind of script provided here:

basitaalishan.com/.../rebuild-all-indexes-on-all-tables-in-the-sql-server-database

Was this reply helpful? Yes No
Suggested answer

Vivian Voss 2 User Group Leader on at

Like (0)

Report

Hi Madu,

as Alex said rebuilding indexes might not solve your problem, but they definitely will help with performance and those you need to do in the SQL database.

Here are some links that might be useful for you:

technet.microsoft.com/.../hh699783.aspx

msdn.microsoft.com/.../gg509027.aspx

technet.microsoft.com/.../hh699840.aspx

Please remember to mark this answer as verified, if you find it useful :-)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

all these specs fine , we have two servers one for application one for sql database server (sql 2014) on windows 2012R2

that's why we thought of running a task to rebuild indexes, we started from CRM 4 and upgraded version by version now in dynamics 365

I have seen one article mentioned about truncating PrincipalObjectAccess table https://blog.westmonroepartners.com/5-ways-to-improve-microsoft-dynamics-crm-performance/

I am not sure this will do the trick or not so i didn't truncate it.

Was this reply helpful? Yes No
Suggested answer

Vivian Voss 2 User Group Leader on at

Like (0)

Report

Hi!

The PrincipalObjectsAccess table was also the one we looked into when we were still on the 2011 version. Here are some more info about that: support.microsoft.com/.../performance-is-slow-if-the-asyncoperationbase-table-becomes-too-large

xrmblog.orbis.de/migration-issue-cleaning-asyncoperationbase-truncate-dublicaterecordbase

Although it shouldn't be a problem in the CRM versions after 2015.

Here is more info about fragmented indexes and rebuilding them: docs.microsoft.com/.../reorganize-and-rebuild-indexes

Do you use ClickDimensions?

We found that the tables for ClickDimensions were also affecting greatly our performance.

Was this reply helpful? Yes No