Managing Load Test Results in the Load Test Results Repository
When you run your load tests, any information gathered during a load test run may be stored in the Load Test Results Repository, which is a SQL database. The Load Test Results Repository contains performance counter data and any information about recorded errors. The Results Repository database is created by setup for controllers, or created automatically on the first local run of a load test. For a local run, the database will be created automatically if the load test schema is not present.
If you modify the controller's results repository connection string to use a different server, the new server must have the loadtestresultsrepository.sql script run to create the schema. For information about how to set up the Load Test Results Repository, see How to: Create a Load Test Results Repository Using SQL.
Visual Studio Ultimate provides named counter sets which collect common performance counters based on a technology. These sets are useful when you are analyzing an IIS server, an ASP.NET server, or a SQL server. All of the data collected with counter sets is stored in the Load Test Results Repository.
There is a difference between a counter set and the performance counter data. A counter set is metadata. It defines a group of performance counters that should be collected from a computer that is performing a particular role such as IIS or SQL Server. The counter set is part of the load test definition. Performance counter data is collected based on the counter sets, the mapping of the counter set to a specific computer, and the sample rate.
- Visual Studio Ultimate
SQL Server 2012 versions
To use load tests, you can use SQL Server 2012 Express LocalDB which is installed with Visual Studio 2012 Ultimate and is the default database server for load tests (including Microsoft Excel integration). SQL Server Express LocalDB is an execution mode of SQL Server Express that is targeted to program developers. SQL Server Express LocalDB installation copies a minimal set of files necessary to start the SQL Server Database Engine.
If you upgrade from Visual Studio 2010 Ultimate and SQL Server Express is detected with an existing load test database, Visual Studio 2012 Ultimate will try to connect to it and use it. Additionally, if SQL Server Express is detected, Visual Studio 2012 Ultimate will try to create the load test database using SQL Server Express instead of SQL Server Express LocalDB.
If your team expects heavy database needs, or your projects outgrow SQL Server 2012 Express LocalDB, you should consider upgrading to either SQL Express or full SQL Server to provide further scaling potential. If you upgrade SQL Server, the MDF and LDF files for the SQL Server 2012 Express LocalDB are stored in the user profile folder. These files can be used to import the load test database to SQL Server Express 2012 or SQL Server 2012.
You can download SQL Server Express 2012 from the Microsoft Download center: Microsoft SQL Server Express 2012.
Load test results store considerations
When Visual Studio Ultimate is installed, the load test results store is set up to use an instance of SQL Express that is installed on the computer. SQL Express is limited to using a maximum of 4 GB of disk space. If you will run many load tests over a long period of time, you should consider configuring the load test results store to use an instance of the full SQL Server product if available.
Load test analyzer tasks
Set up a load test results repository: You can set up a load test results repository on a SQL database.
> [!NOTE] >
A load test repository can also be created when you install a test controller. For more information, see Installing and Configuring Test Agents and Test Controllers.
Selecting and viewing a results repository: You can select a specific results repository. You are not limited to a local results store. Frequently, load tests are run on a remote set of Agent computers. Test results from your agents or your local computer can be saved to any SQL server on which you have created a load test results store. In either case, you must identify where to store your load test results by using the Administer Test Controllers window.
Deleting a load test result from the repository: You can remove a load test result from the Load Test Editor by using the Open and Manage Load Test Results dialog box.
Import and export results into a repository: You can import and export load test results from the Load Test Editor.
You can view the results of both a running load test and a completed load test by using the Load Test Analyzer.