Enterprise Library Test Guide - Willy .Net

Testing for Performance and Scalability 195
Operation Users TPS
Logging Application 50
Block uses MSMQ
trace listener.
Response time
(ms)
Total transactions
Overhead
(percent)
For an explanation of these metrics, see Measuring Performance.
Testing the Data Access Application Block
The tests for the Data Access Application Block use a variety of database access methods.
To avoid external constraints, such as network I/O or disk I/O for SQL Server,
all the queries to the database return small payloads. Most of the test cases read from
the database. Some of the queries were stored procedures and Transact-SQL script
files that were used with the Northwind sample database. Because the target is Enterprise
Library, it was important to ensure that there were no deadlocks or SQL Server
exceptions to contaminate the measurements. For more information, see Tuning the
Test Environment.
Table 11 lists the scenarios for the Data Access Application Block. Here is an explanation
of each of the columns:
● ID. This column lists the ID number for each scenario.
● Scenario. This column lists the Data Access Application Block scenario being
tested.
● Transaction. This column lists that the scenarios are tested both with and without
a transaction.
● Users. This column lists the different numbers of users that the tests simulated.
● Database provider. This column lists the database provider that is used.
Table 11: Data Access Application Block Scenarios
ID Scenario Transaction Users
1 Use a DbDataReader to read With/Without 1, 10, 50, 150,
multiple rows
Transaction 300
2 Use a DataSet to read
multiple rows
3 Use ExecuteDataSet to
execute a stored procedure
that has parameter values
and return the results in a
DataSet.
4 Use ExecuteScalar to
retrieve a single item.
With/Without
Transaction
With/Without
Transaction
With/Without
Transaction
1, 10, 50, 150,
300
1, 10, 50, 150,
300
1, 10, 50, 150,
300
Database
provider
SQL Server
SQL Server
SQL Server
SQL Server
continued