Planning

The System Administrator performs the analysis described in steps 1 and 2 of the algorithm in “Algorithm for successfully distributing engine resources” and decides on the following hierarchy plan:

The OLTP application is an EC1 application and the isql application is an EC3 application.
Login “L1” can run different client applications at different times and has no special performance requirements.
Login “L2” is a less critical user and should always run with low performance characteristics.
Login “sa” must always run as a critical user.
Stored procedure sp_xyz should always run with high performance characteristics. Because the isql client application can execute the stored procedure, giving sp_xyz a high-performance characteristics is an attempt to avoid a bottleneck in the path of the OLTP client application.

Table 5-1 summarizes the analysis and specifies the execution class to be assigned by the System Administrator. Notice that the tuning granularity gets finer as you descend the table. Applications have the greatest granularity, or the largest scope. The stored procedure has the finest granularity, or the narrowest scope.

**Table 5-4: Example analysis of an Adaptive Server environment**
Identifier	Interactions and comments	Execution class
OLTP	Same tables as isql Highly critical	EC1
isql	Same tables as OLTP Low priority	EC3
L1	No priority assignment	None
sa	Highly critical	EC1
L2	Not critical	EC3
sp_xyz	Avoid “hot spots”	EC1