Transaction profile

Using statistics io, showplan, and both dbcc 302 and dbcc 310 to capture application processing details and record transaction profiles. Save showplan and dbcc output for critical transactions. You will use this information as a baseline for post-upgrade testing, as described in Chapter 6, “Ensuring Stability and Performance.”

Create a document similar to the following:

App name

process (xact) name

Type of processing

Xact priority

Freq per user (per hour)

Source code

Required average response time

Required max response time

Current avg/max response time

Trades

addTrade

Heavy OLTP

P1

90

Stored Proc

<2 sec

<5 sec

1 sec avg 3 sec max

Trades

bustTrade

Heavy OLTP

P1

10

Stored Proc

<5sec

<10 sec

2 sec avg 8 sec Max

Trades

reconcileTrades

Batch

P1

1 per day

Embedded SQL/COBOL

<30 min

<60 min

25 min avg 45 min max

Trades

listAccounts

Light OLTP

P1

180

Stored Proc

<2 sec

<5 sec

1 sec avg 2 sec max

NoteIf you are upgrading from Adaptive Server version 12.0 or later, you can save abstract query plans for your critical queries. For more information, see the Performance and Tuning Guide.

See the Performance and Tuning Guide for more information on gathering transaction statistics. Also see ASE Migration Resources Web page for TechNotes and white papers on query processing.