Page History
...
- Configuring IBM DB/2 for Windows, UNIX, and Linux
- Configuring Microsoft SQL Server
- Configuring Oracle
- Configuring Sybase
| Anchor | ||||
|---|---|---|---|---|
|
| Info |
|---|
The connected profiling user should be a member of the DB2 SYSMON group. |
...
This solution must be performed from DB2 CLP, on the DB2 server. If you attempt to perform these tasks through a client, an error message will resultresults.
- Navigate to Start > Programs > IBM DB2/COMMAND LINE TOOLS > COMMAND LINE PROCESSOR.
- Turn the monitor switches on using the following commands:
db2 update dbm cfg using dft_mon_lock on dft_mon_bufpool on dft_mon_sort on dft_mon_stmt on dft_mon_table on timestamp on dft_mon_uow on db2stop db2start - Ensure that the switches are turned on by connecting to the server with the following command:
Db2 connect to database username password password
The following screenshot provides an example of the input and output from the server:
| Anchor | ||||
|---|---|---|---|---|
|
Perform the following tasks to ensure that SQL Server is compatible with Optimizer:
- If you are setting up SQL Server 2000, ensure the current user is a member of the sysadmin group.
- If you are setting up later versions of SQL Server, the current user The current user must meet one of the following requirements:
- Be a member of sysadmin, or have the VIEW SERVER STATE permission enabled.
- Be a member of sysadmin, or have the SELECT permission enabled
On SQL Server 2000 only:
You can enable profiling to capture more SQL by adding the following flag:
DBCC TRACEON(2861)
Trace flag 2861 instructs SQL Server to keep zero cost plans in cache, which SQL Server would typically not cache (such as simple ad-hoc queries, set statements, commit transaction and others). In other words, the number of objects in the procedure cache increases when trace flag 2861 is turned on because the additional objects are so small, there is a slight increase in memory that is taken up by the procedure cache.
...
- .
| Anchor | ||||
|---|---|---|---|---|
|
Oracle users need access to V$ views. In order to configure Oracle to provide users with these privileges:
- If you are setting up Oracle 10 or later, ensure you are logged in as sys or system with the sysdba role, or the SELECT_CATALOG_ROLE has been granted to user_name.
- If you are setting up an earlier version of Oracle, ensure you are logged in as sys or system with the sysdba role.
| Anchor | ||||
|---|---|---|---|---|
|
...
Configuring Sybase
Perform the following tasks to ensure that Sybase is compatible with DB 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.
...
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.