 |
Home > Using Profiling > Configuring Profiling > Configuring DBMS Properties and Permissions > Configuring Sybase
|
Perform the following tasks to ensure that Sybase is compatible with Optimizer:
● Ensure the following system configuration properties are activated:
• Enabling Monitoring (sp_configure “enable monitoring”, 1)
• Wait Event Timing (sp_configure “wait event timing”, 1)
• SQL Batch Capture (sp_configure “SQL batch capture”, 1)
• Max SQL Text Monitored (sp_configure “max SQL text monitored”, 2048) 2048 is the suggested value, must be greater than 0. This defines the maximum size a SQL statement that can be captured.
The following options are specific to Sybase 15.0.2 and higher.
• SQL Text Pipe Active (sp_configure “sqltext pipe active”,1)
• SQL Text Pipe Max Messages (sp_configure “sql text pipe max messages”, 512) 512 is the suggested value, must be greater than 0. This defines the maximum number of SQL statements that Sybase tracks at any given time. You may want to increase this number if you observe a lot of UNKNOWN statements in the Profile Editor.
• Statement Statistics Active (sp_configure “statement statistics active”, 1)
• Per Object Statistics Active (sp_configure “per object statistics active”,1)
Additionally, perform the following tasks, as necessary:
● If a user does not have mon_role enabled, the user will not be able to access Adaptive Server’s monitoring tables.
● If the monProcess table is missing, the user will not be able to view currently connected sessions.
● If the sysprocesses table is missing, the user will not be able to view information about Adaptive Server processes.
● If the monWaitEventInfo table is missing, the user will not be able to view information about wait events.
● If the monProcessSQLText table is missing, the user will not be able to view currently executing SQL statements.
Note: These packages should only be installed by the DBA.
Profiling enables you to create a set of launch configurations to store the basic properties for each profiling session that you run on a regular basis. A launch configuration enables you to start profiling sessions from a single menu command, rather than re-define configuration parameters each time you want to run one.