The two of the most recent SQL Server products I've reviewed were dbWatch and Spotfire. Spotfire is a visualization tool for dashboards and maps. I've reviewed it in a previous article. The Spotfire technique for analyzing large, complex SQL Server instances addressed the issue of how Spotfire addresses the performance and capacity of large SQL Server instances.
DB2 is a high-availability implementation of the SQL standard. DB2 is a direct successor to AS/400. One of the earlier and long-lived implementations of the SQL standard, SQL/DS also based on AS/400, DB2 is the basis for the DB2 Clientless connection to the Database and Database Server in dbWatch. Db2 and dB2 support the dynamic, session-based connection facilities of SQL Server, dbWatch, and I'll describe those in a future installment. Also check back to see how dbWatch works with Oracle and MySQL.
The dbWatch Essentials package gives you a one-time install that will capture metrics from any instances of SQL Server to which it is attached. There are separate installers for Windows 2000 and SQL Server 2000; a single installer will install dbWatch on both operating systems.
Before you launch dbWatch, you must attach to the monitored SQL Server instances. The instructions for this are in the dbWatch documentation. All of the dashboard functions of dbWatch on SQL Server will also run on DB2, MySQL, Oracle, PostgreSQL, and other DBMS environments. That means you can use dbWatch for monitoring of your SQL Servers, but you'll also need dbWatch for Oracle and dB2 if you're using those products. If you're using more than one DBMS, it's important to have as much data collection capability as possible.
Once the dbWatch Essentials software is installed on a monitored server, that server is ready to be monitored. I'll outline how to perform and view each dashboard function in a subsequent installment.
A SURVEY.SQLSERVER.SPOTLIGHT_COLLATABLES template partition is used to avoid performance issues. However, these tables are also used in the Query and Report Cache to keep the Query Cache fresh. The query cache is used to speed up execution of queries on shared tables by storing the results of previously run queries for reuse. In addition, the Query Cache is used to keep the Report Cache fresh. The query cache and report cache are NOT compatible. For example, specify FORCESELECTION ON in the SQL_QUERY option of the SURVEY.SQLSERVER.SPOTLIGHT_CACHE table to avoid performance issues that could occur if reports are stored in the query cache. Also, always verify the first entry in the SPOTLIGHT_CACHE table is set to 0 to indicate the NULL. This avoids deadlocks with the SURVEY.SQLSERVER.SPOTLIGHT_CACHE table. 7211a4ac4a