115
Going forward, DAMS will take care of the index management activities like creating new indexes, rebuild existing indexes and drop unused indexes. These activities will be done as nonintrusive background processes round the clock, which is why the batch job to handle SQL index defragmentation was deprecated.
Please provide the log with activities from DAMS (and other automatic system maintenance) within LCS.
STATUS DETAILS
Needs Votes

Comments

A

It has been still for a while, but hopefully I can add some life to this bright idea. In general, DAMS processes have little transparency.I'm observing indexes that DAMS has created. Some of them make sense, but some are ridiculous. I'm seeing one with 14 key columns and 29 included. This is breaking recommendations for good index design and reduces trust to DAMS as such. Seeing how and if indexes are used, would allow us as a partner make better design decisions, work on user training and have better dialog with MS.

Category: Lifecycle Services

A

Great idea! I know at list two D365FO implementation projects DAMS is not working. On one of the projects, it is the main reason of performance degradation.

Category: Lifecycle Services

A

Access to maintenance information is crucial since some customer consider this part of their internal monitoring. Whether or not LCS is the right place to publish the logs is more doubtful. I would prefer Azure Logs or Insights or something like that.

Category: Lifecycle Services

A

Great idea!

Category: Lifecycle Services

A

Yes please provide DAMS logs but please expose them somewhere other than LCS such as a D365 table. LCS logs have proven to be very difficult to consume in general and with a very limited lifespan.

Category: Lifecycle Services

A

Suggested read on this topic:
https://devblogs.microsoft.com/azure-sql/running-1m-databases-on-azure-sql-for-a-large-saas-provider-microsoft-dynamics-365-and-power-platform/

Category: Lifecycle Services