User Permissions for Sybase

For complete Splunk AppDynamics Database Visibility functionality, the monitoring user requires the permissions listed in the table below.
Permission type Permission
Role permission
  • sa_role
  • mon_role
Select permission
  • master.dbo.monWaitEventInfo
  • master.dbo.sysconfigures
  • master.dbo.sysmonitors
  • master.dbo.monProcess
  • master.dbo.monProcessLookup
  • master.dbo.monProcessSQLText
  • master.dbo.monProcessProcedures
Execute permission
  • sp_sysmon
If you require to browse the objects of a custom database, use the following command: 
use [custom-db-name]
sp_adduser <user-name>
To create a new dedicated user for Splunk AppDynamics Database Visibility, you can use the following sample user creation script. Before running the script, change "password" to a more secure value.
create login 'DBMon_Agent_User' with password 'password' go
exec  sp_locklogin  'DBMon_Agent_User', 'unlock'
go
exec  sp_role 'grant', 'mon_role', 'DBMon_Agent_User'
go
where DBMon_Agent_User is the user name under which you run the Database Visibility Agent.

Also, the following configuration parameters must be set to 1 (true) to monitor the Sybase ASE database with Splunk AppDynamics Database Visibility: "enable monitoring", "wait event timing", "SQL batch capture", and "object lockwait timing". You should also set "max SQL text monitored" to at least 8192 (8kB).

Here is an example of the commands required to configure these settings:
sp_configure "enable monitoring", 1
go
sp_configure "wait event timing", 1
go
sp_configure "SQL batch capture", 1
go
sp_configure "object lockwait timing", 1
go
sp_configure "max SQL text monitored", 8192
go

If the value for "max SQL text monitored" was previously less than 4096, then increasing this setting will require that you restart the Sybase ASE instance.

To monitor Sybase >= 15.7 without the sa_role permission, run these commands:
use sybsystemprocs
grant execute on sp_sysmon to mon_role
Note: If you choose to monitor Sybase using sp_sysmon, you may encounter the following errors:
  • Thread utilization is incorrectly reported. View the official report here.
  • Timeslice error in mmap64 or mda_flush_iostats. View the official report here.