When database objects are accessed by Microsoft SQL Server, the access check is cached in an internal structure that is called the "access check result cache." In rare circumstances, you may experience performance issues if the access check result cache size is too large or too small.
For example, you may want to reduce the size of the access check result cache if too much memory is used. Or, you may want to increase the size of the access check result cache if you experience high CPU usage when permissions are recalculated.
You can use the sp_configure stored procedure together with the "access check cache bucket count" and "access check cache quota" options to control the size of the access check result cache. This article describes the "access check cache bucket count" and "access check cache quota" options that are available in the sp_configure stored procedure.
Note You should change the default values only when a Microsoft Customer Support Services technician advises you to do this.
For example, you may want to reduce the size of the access check result cache if too much memory is used. Or, you may want to increase the size of the access check result cache if you experience high CPU usage when permissions are recalculated.
You can use the sp_configure stored procedure together with the "access check cache bucket count" and "access check cache quota" options to control the size of the access check result cache. This article describes the "access check cache bucket count" and "access check cache quota" options that are available in the sp_configure stored procedure.
Note You should change the default values only when a Microsoft Customer Support Services technician advises you to do this.