
CHAPTER 2 Analyze: Documenting Business Requirements
11
Service Level Requirements
Document application details and service requirements, as in this example:
Transaction Profile
Using statistics io, showplan, and both dbcc 302 and dbcc 310 to capture
application processing details, record transaction profiles. You can plot these
on a chart like the following. Save
showplan and dbcc output for critical
transactions. You will use this information as a baseline for post-upgrade
testing, as described in Chapter 7, “Test: Ensuring Stability and Performance”.
Create a document similar to the following:
CIS every weekend different tables
“Round-robin” every
night
different tables
“Round-robin”
every night
every hour
ACT every weekend different tables
“Round-robin” every
night
different tables
“Round-robin”
every night
every hour
Database
name
Frequency of
dbcc checkdb
and dbcc
checktable
Frequency of dbcc
checkalloc and
dbcc tablealloc
Frequency of
update statistics
Frequency of
monitoring
utilization
Application
name
Type of
application
App.
langs
Client
machines
No. of
con-
current
users
DBs
accessed
Availability
require-
ments
(per day)
Perform-
ance
(average
response
time)
Trades Heavy OLTP C UNIX
work-
stations
220 TRD CIS <5 min
downtime
<2 sec
Customer Light OLTP
DSS
Power-
builder
PC 470 CIS <10 min
downtime
< 5 sec
Accounting Light OLTP
DSS Batch
Power-
builder
PC 345 ACT CIS <5 min
downtime
<5 sec
Marketing DSS C PC 195 MKT CIS <30 min
downtime
<120 sec
Komentáře k této Příručce