How to Reduce the Number of D365 Table Reads for System Tables

(0) Share

Report

Posted on by Ignatius

The D365 system has a custom solution that uses a number of custom tables.

Currently, the users of the system are performing quite a bit of data loading which involves, of course, reading from tables, creating records, and updating records in large quantities and in a concentrated period of time.

However, whenever I look at performance, it shows that two system tables are numbers 2 and 3 in the entity usage.

I have done some research on these two: susbscriptiontrackingdeleteobject and principalobjectaccess.

The information has given some ideas on how to reduce the size (number of records) in the tables after the fact.

Is there a way to reduce the number of reads of these tables? It just seems like quite a bit of resources are being used to constantly read from these two tables.

Thanks.

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Leah Ju Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Partner,

1.SubscriptionTrackingDeletedObject

The SubscriptionTrackingDeletedObject table is the table that logs records for number of days before deleting inactive subscriptions as well as timed out deletion services.

https://powerplatform.se/how-to-reduce-subscriptiontrackingdeletedobject-table-in-cds-dynamics-365/

2.PrincipalObjectAccess

The user can share a record with another user or team, or reassign a record to another user or team.

To manage this record-level collaboration and to provide user access to shared records, all sharing of records and their permissions are stored in the PrincipalObjectAccess (POA) table.

https://learn.microsoft.com/en-us/power-platform/admin/manage-principalobjectaccess-storage

I hope you can verify my answer if it helps you! If you have any questions, please feel free to contact me.
Regards,
Leah

Was this reply helpful? Yes No