Test SQL queries

This type of testing requires that you test a selection of statements that are representative of typical transactions that
the application performs during day-to-day operations. Different applications require different benchmark tests because the
fundamental business use for each application varies. For example, a meter reading application might simply test a basic INSERT
statement. However a mobile sales force application might test multiple INSERT statements, in addition to multiple SELECT
statements and perhaps an UPDATE statement.

The volume of queries in your application can limit what you can realistically test. If you have excessive query processing,
you may be limited to performing the targeted SQL benchmark testing.

If you have a lot of statements used by your applications, you may want to narrow the scope of your test to include some or
all of the following:

The most frequently-used statements.

The statements that process high volumes of data.

The statements that have time-sensitive requirements.

The statements that are most important to the business case of your application.

The most complex statements: for example, those that have the largest number of table joins or that use many subqueries. These
types of statements can use a large amount of device resources. Even if the statements are only used infrequently, you may
want to check that they don't exceed the capacity of the device.