Clean up PrincipalObjectAccess in CRM 2015

(0) Share

Report

Posted on by Community Member

With CRM 2015 On Premises our PrincipalObjectAccess table has grown to about 12M rows, and I've read about possible performance issues after 10m. How can we go about cleaning this up? Something I've noticed is when a share is created then removed it leaves the record in this table with InheritedAccessRightsMask = 0 and AccessRightsMask = 0, which of our 10m rows 4.6m are like this. I've read various sites where people suggest ways to clean this table, but I haven't found anything related to CRM 2015 or anything that doesn't involve updating the database which we avoid like the plague.

So what is the Microsoft suggested or supported way to clean this up? If just removing the Share keeps the database record in the table is direct database modification the only way? And if so what's suggested to delete from this table?

Thanks for any advice.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Jason M. Cosman 5,234 Moderator on at

Like (1)

Report

Hello Sam;

In the past i've cleaned up the PoA table using this article from Microsoft: support.microsoft.com/.../how-to-control-principalobjectaccess-table-growth-in-microsoft-dynamics-crm-2011 . I hope this helps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

From what I'm reading these should be getting purged in the Deletion Service after they are 90 days old, but I'm not sure where this service runs or how to verify it's working. Can someone give suggestions on this? Thanks.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Jason, I read this article earlier, but it appeared to only apply after Update Rollup 6 was added to CRM. I don't see that it's specific to the issue we're running into. Also I really don't like making direct DB changes if there's a supported way of cleaning these up.

Was this reply helpful? Yes No
Suggested answer

prt33k 6,907 on at

Like (0)

Report

Hi Sam,

Usually the deletion service take cares of these kind of record. You can use the codeplex tool to schedule it as per your requirment:

crmjobeditor.codeplex.com/.../574469

You can read more about deletion service here : blogs.msdn.microsoft.com/.../dynamics-crm-2011-deletionservice-async-maintenance-operation-demystified

Thanks,

PS

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Does anyone know if performance issues due to POA, affect all versions of CRM / 365? Or only the oldest ones? Just to know because most posts related to this are regarding to CRM 2011. I think this is the only one I found related to newer versions. Thanks!

Was this reply helpful? Yes No
Suggested answer

ARIFNIIT 1,391 on at

Like (0)

Report

Hi Sam,

I think you can delete records with InheritedAccessRightsMask = 0 and AccessRightsMask = 0. it will not impact your system access right.

InheritedAccessRightsMask = 0 and AccessRightsMask = 0 means no rights.

Was this reply helpful? Yes No