KB strives to explain a high CPU issue on the SQL server. workaround is to create a new index. Only per command auditing customers.
Applies to – All versions of Centrify DA 3.x (per command auditing)
If per command auditing is enabled and if customer is auditing a large number of users/commands, the performance of database insert may get affected because of lack on a certain index on the Session table of active Audit Store database. The lack of index may cause high CPU usage especially when the DirectAudit system is auditing a large number of users or commands. This issue may affect customers who are using per-command auditing more compared to customers who are using shell auditing.
When per-command auditing is enabled, one entry is made in session table of active Audit Store database for each audited command executed by the user. E.g. If customer is auditing dzdo command, there will be x number of rows in session table where x is the total number of times the dzdo command was executed by one or more users. Before this row is inserted, another select query is run which searches session table and performance of this query may be affected depending on amount of data in session table. If there is a large number of rows in session table, lack of index affects the query performance.
Customer can add a new index to the active Audit Store database to speed up the search query.
The following SQL query can be run on active Audit Store database to create the missing index,
CREATE NONCLUSTERED INDEX IX_Session_MachinePrincipal_State_Tty ON [dbo].[Session] ([MachinePrincipal],[State],[Tty]) INCLUDE ([SessionId])
This issue is targeted to be fixed in Centrify Suite 2015