SQL Server concurrent ACL update can corrupt the Read ACL

This is specific to SQL Server when using the Read ACL optimization (activated by default).

Since we have change the isolation NXP-10640, the stored procedure to update the read ACLs may fail (silently) on concurrency.

This means that some ACL changes will not be taken in account on the materialized read ACLs (ACLR tables). These leads to documents not visible in content view, however documents are still accessible using direct URL. Note that there is no security risk because document access is checked using ACL table (and not ACLR).

Rebuilding the ACLR fix this problem (EXEC nx_rebuild_read_acls)

The nx_update_read_acl procedure was implemented to work with a snapshot isolation it should be rewrite to work on read committed isolation.