Dell Power Solutions

More documents

Recommendations

Info

SCALABLE ENTERPRISE• Scale up with IA-64 migration: Replace 32-bit servers with64-bit servers designed to provide applications with greatermemory addressability and storage capability.• Scale out: Restructure the database using a variety ofmethods to provide the required performance. 1This article explores the reasons why and circumstances underwhich organizations may consider 64-bit database technology usingMicrosoft ® SQL Server 2000 Enterprise Edition software as wellas how IA-64 architecture can help remove certain performancebottlenecks cost-effectively.IA-64 components in SQL Server 2000Microsoft SQL Server 2000 Enterprise Edition (64-bit) componentsinclude:• Database server: Core database functionality• Server agent: Alerts and management• Analysis server: Online analytical processing (OLAP) anddata miningThe preceding IA-64 components are code-compatible with the32-bit version of SQL Server 2000, allowing administrators to integratean IA-64 server with other SQL Server 2000 database servers.Capabilities of IA-64 architectureThe enhanced scalability and performance capabilities of SQLServer 2000 (64-bit) is enabled by several features of the 64-bitIntel Itanium ® architecture. Key benefits are as follows.Memory addressability. Generally, 32-bit systems can addressonly a 4 GB address space. See the section “Comparison of SQLServer 2000 (32-bit) with extension technology versus 64-bit IA-64architecture” in this article for more information about optionsavailable with Address Windowing Extensions (AWE) and PhysicalAddress Extension (PAE) on 32-bit platforms. The MicrosoftWindows Server 2003 operating system running on Intel ItaniumIA-64 architecture supports up to 1,024 TB of physical memory and512 GB of addressable memory.Parallel-processing support. Intel Itanium chips include severalfeatures that are designed to enhance parallel-processingperformance compared to 32-bit Intel chips. 2 The Intel Itanium 2chip offers a wider system bus, more registers, 3 and ExplicitlyParallel Instruction Computing (EPIC) technology, which isBecause of their size,designed to enable a processorto execute up to six instructionssome applications may simultaneously. Such performanceimprovements in parallel processingcan help enhance many SQLbe reaching the limitsServer 2000 parallel operations,of the 32-bit platform, including parallel query resolutions,index builds, backup andspecifically regarding restore operations, data loads, andmaintenance operations.number of processors and Enhanced bus architecture.The bus architecture on currentaddressable memory. IA-64 chip sets can provide greaterthroughput than in 32-bit environments.4 More data can be passed to the cache and processorsquickly—an enhancement somewhat analogous to the improvementthat broadband offers over dial-up connections.Comparison of SQL Server 2000 (32-bit) with extensiontechnology versus 64-bit IA-64 architectureMicrosoft SQL Server 2000 Enterprise Edition (32-bit) uses theMicrosoft Windows ® 2000 Server AWE and PAE application programminginterfaces (APIs) to support very large amounts of physicalmemory in applications and the operating system, respectively.For some applications, using AWE to enhance SQL Server 2000 (32-bit) may be a viable alternative to upgrading to the IA-64 platform.Standard 32-bit systems can map 4 GB of memory at most, limitingthe addressable memory space for Windows 2000 systems to4 GB. With 2 GB reserved for the operating system, only 2 GB ofmemory remain for the application—in this case, SQL Server 2000.Administrators can increase the amount of addressable applicationmemory to 3 GB by setting the /3GB switch in the Windows boot.inifile. However, slight performance degradations may occur when usingAWE and PAE in this way, and not all aspects of SQL Server 2000(and many other applications) can take advantage of these extensions.In contrast to the 32-bit limitations, SQL Server 2000 (64-bit)makes extended memory available to all database processes andoperations. When using the 64-bit version of SQL Server 2000 onItanium 2–based hardware like the <strong>Dell</strong> <strong>Power</strong>Edge 7250 server,a SQL Server instance can address up to 512 GB, 5 which is the currentmaximum memory supported by Windows Server 2003. (Thetheoretical addressable limit is 18 exabytes. 6 ) This memory is availableto all components of SQL Server and to all operations within1 For more details on the scale-out option, see The Definitive Guide to Scaling Out SQL Server by Don Jones at http://www.dell.com/sql/ebook.2 For more information, visit http://www.microsoft.com/technet/prodtechnol/sql/2000/evaluate/64btdwc4.mspx.3, 5 For more information, visit http://www.microsoft.com/sql/64bit/productinfo/overview.asp.4 For more information, visit http://www.intel.com/ebusiness/pdf/prod/itanium/wp022404.pdf, http://www.intel.com/design/chipsets/e8870/index.htm, andhttp://www.intel.com/products/server/processors/server/xeon/index.htm?iid=ipp_browse+featureprocess_xeon&.6 One exabyte = 2 60 (1,152,921,504,606,846,976) bytes, or 1,024 petabytes.54POWER SOLUTIONS June 2004
SCALABLE ENTERPRISEthe database engine. As a result, SQL Server 2000 (64-bit) is designedto enhance performance of a wide range of memory-intensive databaseapplications.Usage scenarios for SQL Server 2000 (64-bit)Although SQL Server 2000 (64-bit) is designed to offer significantscalability and performance for many applications—includingSAP ® , PeopleSoft ® , Siebel ® , and other applications that requirefrequent disk caching—not every application will benefit from the64-bit version of SQL Server 2000. This section is designed to helporganizations determine whether it is more appropriate to useexisting SQL Server instances or develop new applications basedon the IA-64 architecture.The improved memory and parallel-processing capabilities ofSQL Server 2000 (64-bit) compared with SQL Server 2000 (32-bit)are compelling in several usage scenarios, including:when writing objects such as hash tables—which cannot fit into theavailable memory—to disk. Moving to SQL Server 2000 (64-bit) canhelp improve the performance of applications experiencing the followingmemory-related performance problems:• Recompilation of stored procedures that were evicted frommemory: The IA-64 environment provides a large plan cachefor high-volume transaction applications using large numbersof stored procedures. This helps reduce the need to compilestored procedures that have been evicted from memory—reducing CPU utilization and reducing query latency.• Resource semaphore waits associated with queries awaitingmemory grants: Multiple queries utilizing large-scalehash joins—especially those executing against a data warehouseand spanning large data sets—can be adverselyaffected by resource semaphore waits.• Enhancing performance for memory-constrained relationaldatabase applications: Helping to alleviate memory constraintsallows a larger percentage of the database—or possiblythe entire database—to reside in memory.• Creating or accelerating large OLAP systems with rapidresponse-time requirements: Fast databases providedecision makers with quick access to simplified views ofcomplex data.• Consolidating multiple Windows-based databases andapplications onto fewer, larger systems: By hosting multipledatabases on a single IA-64 platform, organizations can simplifymanagement, improve storage utilization, and generallyimprove operational efficiency.• Scaling up current applications that are experiencingsignificant growth: Migrating existing database servers thatare outgrowing their current platform does not affect theother tiers of multi-tiered applications.• Replacing UNIX systems and applications: The IA-64platform offers a powerful alternative to UNIX ® systems forhigh-end database servers.Other relational database operations that can benefit fromextended memory include:• Index creation: In a 32-bit environment, index creation,including full-text indexing, is restricted to a 3 GB workspace.• Complex queries: Operations that use sorting, large hashjoins, or hash aggregates to construct complex queries canbenefit from extended memory. Memory-intensive hash joinsare very efficient, but when memory is under pressure, thesequeries may be removed from cache in favor of slowermemory-conserving query plans.• Active stored procedures: Benefits can be achieved for largenumbers of active stored procedures through improved cachecapacity. The IA-64 architecture can help substantially reduceoverall CPU utilization and latency by helping to eliminate theneed to evict procedures from cache and compile repeatedly.• Server cursors: As database objects that applications can useto manipulate data sets, server cursors can more readily bekept in memory, helping to improve performance becausememory access is faster than hard disk access.The following section discusses factors to consider when evaluatingspecific applications for the IA-64 platform.Relational database performance factorsMemory-intensive SQL Server relational database workloads are goodcandidates for SQL Server 2000 (64-bit). Many SQL Server resourcesare restricted to a 3 GB limit in the 32-bit environment, resulting insystems that are starved for memory. Such systems degrade performancebecause applications wait for resources and experience delayswhile processors compile stored procedures that have been evictedfrom cache. These systems may also experience excess disk activityMany I/O-intensive applications can potentially benefit fromloading a larger working data set into memory, which is possiblein the IA-64 environment. Although applications requiring morememory than the 64 GB limit supported by AWE are rare, certainapplications or workloads can benefit from the speed of extractingdatabase pages from extremely large cache memory instead of thedisk subsystem.Additionally, the improved in-processor parallelism capabilitiesof IA-64 chip sets as compared to 32-bit chips benefits SQL Server2000 (64-bit) in situations where context switching degrades performance.Administrators can configure SQL Server 2000 to use fiberswww.dell.com/powersolutions POWER SOLUTIONS 55
Page 1 and 2:
DELL POWER SOLUTIONS • JUNE 2004
Page 5: Emulex HBAs. Proven choice of the w
Page 10 and 11: EXECUTIVE INSIGHTSPlanning for the
Page 12 and 13: SCALABLE ENTERPRISEVirtualization a
Page 14 and 15: SCALABLE ENTERPRISEhardware layer.
Page 16 and 17: DELL KNOBuild a scalable enterprise
Page 18 and 19: GET ANSWERSNOW.WE’LL PROVIDE:Cost
Page 20 and 21: SCALABLE ENTERPRISEUsersGlobaldataA
Page 22 and 23: SCALABLE ENTERPRISEAcross entiredat
Page 24 and 25: SCALABLE ENTERPRISEUsing Virtual Ma
Page 26 and 27: SCALABLE ENTERPRISE1.1.10.*1.1.20.*
Page 28 and 29: SCALABLE ENTERPRISEComparison crite
Page 30 and 31: SCALABLE ENTERPRISEEach Dell PowerE
Page 32: SCALABLE ENTERPRISEOperating system
Page 35 and 36: SCALABLE ENTERPRISEBoot server toDe
Page 37 and 38: More data? Less time?No problem.Del
Page 39 and 40: SCALABLE ENTERPRISEEnabling a Highl
Page 41 and 42: Choose Dell coupled with Microsoft
Page 43 and 44: SCALABLE ENTERPRISEto an equal numb
Page 45 and 46: SCALABLE ENTERPRISEFigure C. Select
Page 47 and 48: SCALABLE ENTERPRISELoad-generation
Page 49 and 50: SCALABLE ENTERPRISETopologyPowerEdg
Page 51 and 52: SCALABLE ENTERPRISEIn December 2003
Page 53 and 54: They’re looking to you to solve t
Page 55: SCALABLE ENTERPRISEBuilding a Highl
Page 59 and 60: SCALABLE ENTERPRISEIT staff may cho
Page 61 and 62: SYSTEMS MANAGEMENTFigure 3. Command
Page 63 and 64: SYSTEMS MANAGEMENTMaintaining Netwo
Page 65 and 66: Dave is on vacation.He’s been not
Page 67 and 68: SYSTEMS MANAGEMENTaccess to key net
Page 69 and 70: SYSTEMS MANAGEMENTWMI consumersWMI
Page 71 and 72: SYSTEMS MANAGEMENTstrComputer = WSc
Page 73 and 74: SYSTEMS MANAGEMENTUnattended Server
Page 75 and 76: SYSTEMS MANAGEMENTCreate aRAM drive
Page 77 and 78: SYSTEMS MANAGEMENTTo deploy the IT
Page 79: SYSTEMS MANAGEMENTDell OpenManage S
Page 82 and 83: SYSTEMS MANAGEMENTAssistant 8.x OS
Page 84 and 85: SYSTEM ARCHITECTURENumber of memory
Page 86 and 87: SYSTEM ARCHITECTUREspace, large cac
Page 88 and 89: SYSTEM ARCHITECTUREIntelligent Chas
Page 90 and 91: SYSTEM ARCHITECTUREUnderstandingPer
Page 92 and 93: SYSTEM ARCHITECTUREis to avoid opti
Page 94 and 95: SYSTEM ARCHITECTURE• Low frequenc
Page 96 and 97: STORAGEDesigning and OptimizingDell
Page 98 and 99: STORAGEDell/EMC CX series arrays Ba
Page 100 and 101: STORAGEconstant prefetching. Depend
Page 102 and 103: STORAGELTO-2 tape drives. 3 Archite
Page 104 and 105: STORAGEMoving TowardStorage Virtual
Page 106 and 107:
STORAGE5-disk RAID-5RAID group 64-d
Page 108 and 109:
STORAGEDeriving Maximum Performance
Page 110 and 111:
STORAGEResponse time (ms)2.01.51.00
Page 112 and 113:
STORAGEAchieving ComprehensiveEnter
Page 114 and 115:
STORAGE.doc fileDesktop at headquar
Page 116 and 117:
MAILSTOP 8456DELL INCONE DELL WAYRO
Page 118 and 119:
LINUXSatellite Server and the serve
Page 120 and 121:
LINUXthe most recent Navisphere Age
Page 122 and 123:
LINUXmemory and processors, andsets
Page 124 and 125:
LINUXuser to choose a boot image,an
Page 126 and 127:
LINUXChannel storage device, or eve
Page 128 and 129:
HIGH-PERFORMANCE COMPUTINGIndustry
Page 130 and 131:
HIGH-PERFORMANCE COMPUTINGapplicati
Page 132 and 133:
HIGH-PERFORMANCE COMPUTINGsuch as m
Page 134 and 135:
HIGH-PERFORMANCE COMPUTINGengineers
Page 136 and 137:
HIGH-PERFORMANCE COMPUTINGAs in the
Page 138 and 139:
SECURITYDefending Networks withIntr
Page 140 and 141:
SECURITYTarget server(HTTP server)I
Page 142 and 143:
There are tech reasons to love Linu
Page 144 and 145:
CREATE TABLE ORDERLINES(ORDERLINEID
Page 146 and 147:
DROP PROCEDURE BROWSE_BY_ACTORGOUSE
Page 148 and 149:
ONLINE-EXTRA CONTENTUsing WMI Scrip
Page 150 and 151:
ONLINE-EXTRA CONTENTUsing Dell Open
Page 152 and 153:
ONLINE-EXTRA CONTENTInstalling the
Page 154:
[**] [1:524:6] BAD-TRAFFIC tcp port
show all

Dell Power Solutions

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?