generate barcode in vb.net Lesson 5: Choosing a Version of Windows and SQL Server in Visual C#.NET

Maker UPC Code in Visual C#.NET Lesson 5: Choosing a Version of Windows and SQL Server

Table 1-13 Operating System Requirements: SQL Server 2005 Enterprise Edition (X64),

Standard Edition (X64)

Versions Supporting SQL Server 64-bit X64 Standard Edition Service Pack 1, 64-bit X64 Enterprise Edition Service Pack 1, 64-bit X64 Datacenter Edition Service Pack 1

What are the operating system and SQL Server versions required for threenode failover clustering The operating system requirement is Windows Server 2003 Enterprise Edi tion (or Windows 2000 Advanced Server), and the SQL Server version requirement is SQL Server 2005 Enterprise Edition.

You need to make sure that your choice of SQL Server 2005 and of Windows support your business requirements. Although there are five editions of SQL Server 2005, most organizations choose Enterprise Edition, Standard Edition, or Workgroup Edition. Enterprise Edition has full support for failover clustering and Database Mirror ing. Standard Edition has limited support for these features. Certain versions of SQL Server run only on certain versions of Windows. For example, SQL Server 2005 Enterprise Edition does not run on Windows XP Pro fessional but SQL Server 2005 Standard Edition does. In addition, SQL Server features require certain operating systems. For example, both failover clustering and AWE require Windows Server 2003 Enterprise Edi tion or Datacenter Edition.

You can use the following questions to test your knowledge of the information in Les son 5, Choosing a Version of Windows and SQL Server. The questions are also avail able on the companion CD if you prefer to review them in electronic form.

1

Answers to these questions and explanations of why each answer choice is right or wrong are located in the Answers section at the end of the book.

1. On which versions of Windows can SQL Server 2005 Standard Edition (32-bit) run (Choose all that apply.) A. Windows 2000 Professional Service Pack 4 B. Windows XP Professional Service Pack 2 C. Windows Small Business Server 2003 Standard Edition Service Pack 1 D. Windows 2003 64-bit X64 Standard Edition Service Pack 1 2. Which versions of SQL Server 2005 support failover clustering (Choose all that apply.) A. SQL Server 2005 Express Edition B. SQL Server 2005 Workgroup Edition C. SQL Server 2005 Standard Edition D. SQL Server 2005 Enterprise Edition

To further practice and reinforce the skills you learned in this chapter, you can per form the following tasks:

Review the chapter summary. Review the list of key terms introduced in this chapter. Complete the case scenario. This scenario sets up a real-world situation involv ing the topics of this chapter and asks you to create solutions. Complete the suggested practices. Take a practice test.

Summary

Capacity planning is the process of predicting hardware needs. Choose as many processors as necessary to keep utilization below 75 percent. A basic guideline for database server storage is to place the operating system and SQL Server together on a mirrored drive, the transaction log on a second mir rored drive, and the data files on a third RAID 5 or RAID 10 array. To best estimate memory requirements for your database server, you should per form load testing. If load testing is not feasible, you can add together the mini mum system memory requirements, the buffer cache memory requirements, the procedure cache memory requirements, the connection context memory requirements, and the memory requirements of any additional applications that will be run on the database server. You need to make sure that your choice of SQL Server 2005 and of Windows support your business requirements.

Do you know what these key terms mean You can check your answers by looking up the terms in the glossary at the end of the book.

capacity planning compiled plan data cache database page cache executable plan execution context execution plan kernel mode load testing /PAE plan cache procedure cache query cache query plan query plan cache scaling out scaling up service level agreement (SLA) sizing user mode