Re: ZERO Impact Performance Monitor for Informix BETA program

> The only requirement is that the Sql Power SniFFFer runs on the same > subnet (or on the platform the database server runs on) as the database > server. This allows the Sql Power SniFFFer to view and analyze the SQL > network packet flow to the database server. > > The products require no operational or software changes to the database > server, network or end-user workstations. I assume this can't handle clients who use shared memory connections?

Chuck, Per your question, the following explains the situations under which the Sql Power SniFFFer can or cannot with ZERO required impact - monitor at the SQL transaction level an Informix database server. Please let me know if there are any scenarios I missed. A. The Sql Power SniFFFer or 7x24 Global Monitor products can capture or monitor all or any subset of the SQL transaction performance (or database server service level statistics) sent across a network under the following scenarios: A.1. A connection is made to an Informix database server over the network. The connection can be from a program, end-user, developer or DBA using ODBC, CLI, ESQL, C++, etc. to connect to the Informix database server. Currently DECnet, FDDI, TCP/IP and Token Ring are supported. Other protocols such a Novell can be easily added given market demand. A.2. An end-user, developer or DBA telnets over the network to the platform the Informix database server is running on. Then from the telnet session runs a program such as DBACCESS, etc. to issue SQL to the Informix database server. The connectivity to the Informix database server can be anything. e.g. SHARED MEMORY CONNECTIONS, IPC, ODBC, CLI, ESQL, C++, DECnet, TCP/IP or Token Ring. A.3. LOOPBACK SQL transactions on AIX (available in a few weeks). A loopback SQL transaction is one where the SQL is not sent across the network. e.g. a batch program running on the same platform as the database server connects to the Informix database server using TCP/IP. B. The product line cannot monitor the following situations (at least not yet): B.1. LOOPBACK SQL transactions for Informix database servers running on NT or Solaris . e.g. A batch program running on the same platform as the database server connects to the Informix database server using TCP/IP. The SQL would be sent over the LOOPBACK port to the Informix database server and is not sent over the network. B.2. A batch program running on the same platform as the database server connects to the Informix database server using SHARED MEMORY CONNECTIONS. This scenario is similar to B.1, i.e. LOOPBACK SQL transactions. Note: Please refer to A.2 since the SQL for a SHARED MEMORY CONNECTION is captured and monitored by the Sql Power SniFFFer if the SQL was issued across the network (e.g. telnet session). C. Miscellaneous comments: C.1 The functionality for the monitoring of a SHARED MEMORY CONNECTION when the SQL was issued across the network (e.g. telnet session) will be available next week. C.2 A Sql Power SniFFFer or 7x24 Global Monitor product running on 95, NT, Solaris or AIX can monitor an Informix (IDS) database server running on another operating system (DEC UNIX, i386 UNIX, HP-UX, NCR, SCO UNIX, Stratus, etc.) as long as the product runs on a platform on the same subnet as the database server. i.e. per the above discussion. C.3 The HP-UX version of the product will be available in the near future. Randy Reiter Sql Power Tools www.sqlpower.com 201.825.9511 Chuck Renaud wrote in message <7cp63b$6e1$1@news.xmission.com>... > >> The only requirement is that the Sql Power SniFFFer runs on the same >> subnet (or on the platform the database server runs on) as the database >> server. This allows the Sql Power SniFFFer to view and analyze the SQL >> network packet flow to the database server. >> >> The products require no operational or software changes to the database >> server, network or end-user workstations. > >I assume this can't handle clients who use shared memory >connections?