Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-11267: Performance Issues When Opening Some Centrify Reports in SQL Server 2014

Authentication Service ,  

29 October,18 at 09:18 PM

Problem:

The performance for opening some Centrify reports on SQL Server 2014 is not good enough if its database compatibility level is 120.
 

Root cause:

For the same SQL query, SQL Server 2014 cardinality estimator (CE) uses different execution plans if the database compatibility level is 120.
 

Solution:

Changing the database compatibility level to 110 using the following SQL statement will help alleviate this issue:
 

ALTER DATABASE <database name>
SET COMPATIBILITY_LEVEL = 110

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6041: How to show current license type in use by adclient articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-8464: Report Services Running Slow with SQL Server 2014 article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part I articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out?