performance
Andreas Lommel asked how to test the performance of a 7.30 Solaris database server. Andreas Bettin answered to use onstat -a. Randy Reiter pointed to a commercial Zero Impact Service Level Monitor that measures response times at SQL statement level. An unrelated message asked about wrong deccvasc() results in the CISAM library on a Stratus HP/UX machine; it got no reply.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi, How can I test the performance of my db-server ? (7.30 solaris)
Has anyone experienced a problem with the conversion routines in the CISAM library (specifically "deccvasc()") that result in incorrect converted values? If I run the executable on an HP platform running HP/UX 10.20b, it works fine (an ascii numeric string which is a field in a data record is converted to a valid hexidecimal value prior to writing the record to disk). However, when I run the executable on another machine (a Stratus POLO running HP/UX), the same routine results in an incorrect hexidecimal value, which results in duplicate records (because the field is a key). Could it be a shared library problem?? Sent via Deja.com http://www.deja.com/ Share what you know. Learn what you don't.
Use onstat -a
Andreas Lommel <him_lommel@t-online.de> schrieb in im Newsbeitrag:
379d66c4.4002715@news.btx.dtag.de...
> Hi,
> How can I test the performance of my db-server ? (7.30 solaris)
The Zero Impact Service Level Monitor will measure the end user response time, database server response time, as well as several other database server service level metrics. The measurement are performed at the SQL statement level. The product requires no impact upon the databse server, the network or client work stations. Installation is a few minutes. Refer to www.sqlpower.com. Andreas Lommel wrote in message <379d66c4.4002715@news.btx.dtag.de>... >Hi, >How can I test the performance of my db-server ? (7.30 solaris)