
CHAPTER 7 Test: Ensuring Stability and Performance
89
Test Cycle: Testing for Performance
This section expands on performance benchmarking before and after upgrade.
For a summary of the entire test cycle, see,“Test Cycle: Summary of Tests” on
page 10.
This section covers the following tasks:
• Pre-Upgrade Single-User Tests
• Pre-Upgrade Multi-User Tests
• Test System Upgrade
• Post-Upgrade Single-User Tests
• Post-Upgrade Multi-User Tests
Note Benchmarks test server processing speed. Therefore, run your
benchmarks from a light-weight client so that all processing happens at the
back-end.
Pre-Upgrade Single-User Tests
After you create the test system at the same ASE level as the production system
and before running benchmarks, you need to sync the test system with the
production system so that comparisons to the new server are valid.
Optimizer
Compare showplan and output from dbcc 310 and 302 which you gathered in
Chapter 2, “Analyze: Documenting Business Requirements”, to that of the test
system to verify that the optimizer is making the same decisions. Some
possible causes of optimizer differences include:
Final migration plan
testing
• Ensure that you are fully prepared by walking
through the upgrade/migration plan.
• Verify that fallback procedures work.
• Identify and test the contingencies.
Walk through every upgrade
step, including fallback
strategies
Stage Purpose Best Technique
Comentarios a estos manuales