Test results are stored in a database. There are four types of settings that can be configured:
- How much data to store: Specify what type of information should be saved (reports, test log, etc.).
- Session content: Specify how many details to store in the test log.
- Data storage medium: Specify what database type to use.
- Agent to controller replication: Specify if you want to copy information to the controller about sessions issued by the agents with SQL Server CE-based storage. This information is necessary for waterfall charts.
1. Go to Result Storage node in the Workflow Tree .
2. Configure what data to store by selecting one of the How Much Data to Store property values:
- All: All the resulting data, including a summary report, all result grids, graphs, and all request/response session info (this is the largest part).Use this mode if you would like to view individual request/response info of replayed sessions.
- Partial: All the resulting data, including a summary report, all result grids, graphs, but no request/response session info.
- None: No info result info is stored. You can view the resulting summary report, all result grids and graphs, but they will be deleted once you run another test or close the test. Use this mode for quick practice tests. No other settings will apply in this mode.
3. Select what database type to use by selecting Data Storage .
- Embedded SQL Server CE: Every test run will have its own database file with up to 4 GB of data. It can store a test log with up to 4 million sessions with the average session size (excluding the response body) up to 1 KB.
- SQL Server: Provide your SQL Server to store virtually unlimited test logs.
4. If Embedded SQL Server CE: is selected, the property Save sessions from agents will be available. In distributed tests with SQL Server CE-based storage, the content of the sessions generated on the agents is stored on the agents.
- Select Yes, to copy this content to the controller. This will allow generating waterfall charts for VUs emulated on the agent.
- Select No, to reduce the traffic between agents and controller when the network bandwidth is limited.
5. If SQL Server is selected, enter a SQL Server Connection String property or ...
6. Click the box in the property grid to bring up the connection string dialog
- Enter SQL Server name, authentication type, credentials and database name.
- Click Create/Check DB. If you use a new database, all tables and other database objects will be created automatically. If use an existing database, the connection will be verified.
- If you selected All during step #2, then most of your data storage will be occupied by the request/response bodies that are stored in the test log. You can reduce the amount of stored data by selecting one of the purge options:
SQL Server CE Notes:
SQL Server Notes:
- The user specified in the Login section should be a database owner (dbo) to have sufficient permissions to create tables and other objects as well as insert and update data. If you specified a new database, the user should have permission to create databases.
- The network connection between the StresStimulus controller and SQL Server should be fast enough to transmit real-time insert transactions. VPN or WiFi networks maybe not fast enough. If StresStimulus determines that the network connection slows down the test execution, it will stop the test and display a slow connection error message.
- If you use load agents that run as a Windows service, then SQL Server Windows Authentication will not work. This is because load agent Windows services run under Local system account. In this case always select SQL Server Authentication.
- Increase the default SQLCommand Timeout property (c) when you have large tests and get errors like: Timeout period elapsed prior to completion of the operation.
- Purge Session Content property (d)
- Static Mime Types: (Default) Request and response content (headers and bodies) of images, video and other static resources are purged. Dynamic content meaningful for performance analysis will be stored.
- None: No request and response content is purged, all content is stored in the database.
- Non-Errors: Non-Error request and response content is purged and error content is not.
- All: All request and response content is purged, no response bodies are stored in the database.
Info: When you enable purging response bodies, some responses will not be stored in the test log. Session inspector will display the message "StresStimulus truncated" in the place of the response content when you open a session with the purged response.