You define transactions to measure the performance of the server. Each transaction measures the time it takes for the server to respond to specified Vuser requests. These requests can be simple tasks such as waiting for a response for a single query, or complex tasks, such as submitting several queries and generating a report.
To measure a transaction, you insert Vuser functions to mark the beginning and the end of a task. Within a script, you can mark an unlimited number of transactions, each transaction with a different name.
For LoadRunner, the Controller measures the time that it takes to perform each transaction. After the test run, you analyze the server's performance per transaction using the Analysis' graphs and reports.
Before creating a script, you should determine which business processes you want to measure. You then mark each business process or sub-process as a transaction.
Avoid using a "," or "@" symbol in a transaction name. These characters may cause errors to occur when attempting to open the Analysis Cross Results graphs.
You can create transactions either during or after recording. For task details, see Insert Transactions.