Quote:
Originally Posted by db2girl
1. The the number of transactions per hour.
2. The average response time per transaction.
3. The average and peak number of "users".
4. The average and maximum size of the transactions
|
You really need more context to answer that. DB2 may have a different concept of transactions (UOW) than the application that connects to it. What is considered a single transaction from the application standpoint may generated multiple UOWs, and vice versa. Ditto response time per transaction.
Number of "users" is even more confusing. In most cases you have some sort of middleware sitting between the application and the database, and DB2 only sees one "user" (authorization ID) and a bunch of constantly open connections coming from a pool. On the other end of the pipe it can translate into thousands of application "users" "connecting" and "disconnecting" all the time, and there is no way DB2 even knows about that.