 |
|
|
 | Control Panel |  | 602SQL Development and Management Client | SQL Console |  |
This page allows you to select a 602SQL Server that will be monitored. The other tabs on this window can be accessed after a server is selected from the Monitoring server combo.
Client access is locked: An exclusive access to the server is guaranteed to the user (administrator) by checking this box. All other connections will be refused. This action will result in a failure if there is another client or thread already connected to the server.
Background processes are enabled:
The username of the user connected to the server and membership to the administrator groups is displayed in the central part of the window. This membership affects the extent of actions the user can do in this window.
You can set the refresh interval (in seconds) on the list of clients, locks and log contents.
A list of all client threads connected to the 602SQL Server is displayed on this tab. Each thread is in a single grid row. One thread exists for each connected user. System threads are run by the server itself (in the Working column designated with 1=Yes), and separate threads executed by the CALL DETACHED command (in the Detached column designated with 1=Yes).
The rows and columns in the grid contain the result of the system query _IV_LOGGED_USERS.
If automatic refresh is not set (Monitor tab), it is necessary to refresh the list manually using the Refresh the list action from the grid pop-up menu.
The Interrupt the client operation allows the selected user to stop a process on the server (e.g. hung procedure, etc.). You may not break system thread or separate thread.
The Disconnect the client action disconnects the selected user. You cannot disconnect yourself, a working thread or separate thread. The disconnected user receives a message that the server terminated the process.
If it is necessary to terminate the working of a system thread, use the checkbox Background processes are enabled on the Monitor tab. More information about disconnecting various clients and their reaction can be found here.
All locks that are placed on table records or object definitions during development (system object locks) and memory pages locks (locking internal structures such as indexes), are listed here. One record in the grid is equivalent to one lock placed in the query result.
The rows and columns in the grid contain the result of the query system query _IV_LOCKS.
The query result may be large when refreshing data and will consume server resources. Keep this in mind if you set a short interval for automatic refreshing.
The Remove the lock action removes the selected lock. You should not execute this action under normal circumstances. Lock are placed by the 602SQL Server. However, if a client is terminated incorrectly, some locks may still exist. It easier to remove the locks from this tab, than restart the entire 602SQL Server.
Some internal specifications of the server are displayed here (the function Get_server_info returns the same information). They can be used for solving problems.
The Total number of opened cursors value specifies the number of cursors opened by all clients.
The Number of opened cursors by the current user value specifies the number of cursors open by the client currently working with the Monitor. The value must be lower or equal to the previous value.
The Number of temporary tables is the number of temporary tables created in the memory (e.g. when evaluating grouped queries).
The Memory used by the server entry is the memory size allocated by the 602SQL Server. This value normally fluctuates during normal server operation but will stabilize after some time. If this value increases indefinitely, an error will occur Out of memory (145). This can cause serious data damage.
A list of trace requests is displayed on this page. It is possible to modify the list directly by editing the grid, add another request by editing the last row or remove a request using the Remove the trace request action from the pop-up menu.
The Create a new temporary log action opens a dialog to specify the parameters of a new log. The log will be added to the log list in the Log name column and may be used for some requests. A new tab with the log name will be added after the Basic log tab.
The basic log entries of the monitored 602SQL Server are displayed in this tab. The basic log format (as for temporary logs) may be modified using _sqp_define_log function. The log contents (what is being logged) is specified in the request list on the Trace tab.
An edit field that contains the selected log item is in the bottom part of the tab. It is used to copying the item to the clipboard and pasting it to another location.
| Control Panel | | 602SQL Development and Management Client | SQL Console | |