APE has the following two database options to select from.
Your choice of which database to test with depends on the data access requirements of your application. While the Jet engine is behind what are sometimes referred to as a personal databases, it can handle a moderate number of simultaneous users. If your application is small and does not require the benefits of a large-scale database, you might want to test (and ultimately implement) your application using Jet.
If you are modeling an enterprise application that requires a robust, high-performance database, you should test using SQL Server. With the SQL Server test option, you can actually modify the APETEST database tables and queries to represent your application's final data access requirements.
The default query statements that APE uses are stored in the ApeQuery table in the Apetest.mdb database. You can use Microsoft Access to change these queries or add some of your own. One useful idea is to add a simple query such as exec myproc and then create a stored procedure in SQL Server with the same name. In this way, you can execute an APE test that realistically runs your own custom stored procedure.
Tip If you insert your own query into the ApeQuery table, be sure to use the Applications Service Options dialog box to select the query.
For More Information For more information on installing the APETEST database for SQL Server, see Installing Application Performance Explorer.