原文是E文，做一下翻譯并且提取一些重要的思路。

1.定義業務規格

• What are your most critical business processes and how often are they processed (e.g. number of sales activities per day, number of client requests per day, etc.)
• 最重要的業務流程是什么，使用頻率如何
• What is regarded (required) as acceptable response times from the online application? How about reports?
• 可以接受的在線應用程序的響應時間是多少，報告又如何
• How much data must be kept available on the live database (over 1 month, 1 year, 5 years?). Can data be archived? How and when?
• 數據在live數據庫中要保存多久，可不可以歸檔，如何歸檔，什么時候歸檔
• How many concurrent application users are expected?
• 并發的用戶數是多少
• Are there periods of more than average usage? (E.g. Daily between 9:00 A.M. and 10:00 A.M. /yearly ’round about Christmas.) What business processes will be impacted the most?
• 業務的高峰期在什么時候，那些流程會被影響
• How much data latency is acceptable for reports?
• 報表數據延遲，多少時間內可以接受
• Etc.
• 等等

2.分析業務

• How many inserts/updates/deletes/selects will be performed on the most important database objects when the database is averagely stressed? How much when there is a period of more than average usage?
• 在平均負載的情況下，在重要的數據庫對象中，有多少insert，delete，select會發生。在業務高峰期有是多少
• How large will your database core objects become (over 1 month, 1 year, 5 years)?
• 若干時間后，數據庫的核心對象會變得多大？
• How many concurrent database users are expected? (This is not equal to application users if connection pooling is implemented.)
• 數據庫的并發量是多大
• What should be regarded as acceptable database response times? For online requests/for reporting requests?
• 可以接受的數據庫響應時間是多少

3.定義磁盤子系統的需求

• 可以使用sqlio 來測試 磁盤子系統
• 也可以使用 SQLIOStress
• 如何達到標準文章并沒有提及，可以根據業務繁忙時段，io的吞吐量也確定，多少才能滿足要求

4.為準備腳本

• Ask a business user to perform a realistic work process as he would in real life situation, including realistic intervals between tasks.
• 咨詢終端用戶實際工作流程，真實的工作狀況，包括任務之間的時間間隔
• Trace this activity using SQLProfiler (only? textdata ?and? starttime ?are important)
• 使用SQLProfiler跟蹤操作
• Replace variables with placeholders for parameters that can be defined at random. (This is where you wanted all database interactions to be performed using stored procedures.)
• 使用隨機數來代替用戶操作的變量
• Add think times to the script.
• 增加延遲
• 相關的操作作者給出了代碼，可以參考原文

5.添加虛擬用戶

• 相關的操作作者給出了代碼，可以參考原文

6.添加測試數據

• 可以使用DTS或者SSIS初始化數據

7.監控

I cover this topic in my previous article on? Monitoring .

8.迭代測試

It is important to run multiple iterations using different parameter combinations but you also need to perform multiple iterations of the same scenario to avoid accidental external impact.

　　使用不同的參數組合迭代測試十分重要，你也需要執行在同一個場景下執行迭代測試來避免意外情況的影響。

原文： SQL Server Monitoring in 8 Steps: Lessons From the Field ?- 02 Aug 2005

數據庫壓力測試思路