Slow Performance on the Server That Stores the OnePoint Database (295836)
The information in this article applies to:
- Microsoft Operations Manager 2000
This article was previously published under Q295836 SYMPTOMS
You may experience slow performance on the server that stores the OnePoint database.
CAUSE
This issue can occur because the Data Access Server does not cache Microsoft SQL Server 2000 connections at any point during its normal interaction with the server that stores the OnePoint database. New SQL Server connection, session, and data bindings are established for each request. This added work can slow down the server's performance.
WORKAROUND
To work around this issue, increase the number of available SQL Server connections beyond the normal requirements. Extra connections allow establishment of new sessions with the database while earlier connections are still waiting for SQL Server to close them.
Also make sure that enough memory is allocated to SQL Server. Each connection requires 30 to 50 kilobytes (KB) of memory. For detailed information about the amount of memory that each connection requires, refer to the SQL Server 2000 documentation.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 6/13/2005 |
|---|
| Keywords: | kbbug kbenv KB295836 |
|---|
|