Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Microsoft SQL Server 2008 R2 Unleashed- P160:SQL Server 2005 provided a number of significant new features and enhancements over what was available in SQL Server 2000. This is not too surprising considering there was a five-year gap between these major releases.Microsoft SQL Server 2008 is not as much of a quantum leap forward from SQL Server 2005 | 1534 CHAPTER 41 A Performance and Tuning Methodology Performance and Tuning Design Guidelines We outline some of the major performance and tuning design guidelines here. There are of course many more but if you a least consider and apply the ones outline here you should end up with a decently performing SQL Server implementation. As we have described previously performance and tuning should first be designed in to your SQL Server implementation. Many of the guidelines discussed here can be adopted easily in this way. However when you put off the performance and tuning until later you have fewer options to apply and less performance improvement when you do make changes. Remember addressing performance and tuning is like peeling an onion. And for this reason we present our guidelines in that way layer by layer. This approach helps provide you with a great reference point for each layer and a list you can check off as you develop your SQL Server-based implementation. Just ask yourself whether you have considered the specific layer guidelines when you are dealing with that layer. Also several chapters take you through the full breadth and depth of options and techniques introduced in many of these guidelines. We point you to those chapters as we outline the guidelines. Hardware and Operating System Guidelines Let s start with the salient hardware and operation system guidelines that you should be considering Hardware Physical Server Server sizing CPUs Physical or virtual servers that will host a SQL Server instance should be roughly sized to handle the maximum processing load plus 35 more CPUs and you should always round up . As an example for a workload that you anticipate may be fully handled by a four-CPU server configuration we recommend automatically increasing the number of CPUs to six. We also always leave at least one CPU for the operating system. So if six CPUs are on the server you should allocate only five to SQL Server to use. You can find details on .
