Required Sybase Permissions

Ignite will set up a login with SA_ROLE and MON_ROLE privileges or use an existing login with those privileges, in order to monitor a SYBASE Instance and perform 'Query Plans' for the sql statements that it captures.  Ignite uses this login to view 4 MDA tables (monProcess, monProcessProcedures,monProcessSQLText, and monProcessLookup) and records information for each active session into a performance warehouse. The query plans are performed on the monitored database, then stored for historical access in the performance warehouse.

Ignite, also, configures the SYBASE Instance with the following configuration:

sp_configure 'max SQL text monitored', 4000'
sp_configure ‘enable monitoring’,1
sp_configure ‘wait event timing’,
sp_configure ’SQL batch capture’,1
set cis_rpc_handling on

Note: The SYBASE Instance must be restarted if the 'max SQL text monitored' wasn't initially 4k.

Changing IGNITE so it does not require SA_ROLE

Ignite requires the SA_ROLE permission during the wizard setup of  monitoring and for collections of 'Historical Query Plans' .  If the 'Historical Query Plan' feature is not required, it is possble to remove the SA_ROLE once monitoring is set up.   In some versions of Sybase, you may need to explicity grant select access on the monProcess, monSysStatement, monTableColumns and monProcessSQLText tables. 

To turn off 'Historical Query Plan' collections so Ignite won't log errors, bring up Ignite > Options > Advanced Options and select the Instance in the lower right hand corner.  Look for the 'PLAN_COLLECTION_ENABLED' option in the list underneath the selected Instance and change the parameter to 'FALSE'.