1 / 10

Effective Strategies for SQL Server Database Consolidation

Discover the ins and outs of SQL Server database consolidation with Denny Cherry, a seasoned database administrator and architect. Learn why consolidation is beneficial, including reduced server count and cost savings on licenses, power, and cooling. Explore different consolidation techniques such as multiple databases in a single instance or multiple instances on a single server. Understand when consolidation works best and when it might not be effective. Equip yourself with the knowledge to make informed decisions about your SQL Server infrastructure.

malana
Télécharger la présentation

Effective Strategies for SQL Server Database Consolidation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Can I really consolidate my SQL Server database? Denny Cherry Senior Database Administrator / Architect dcherry@awarenesstech.com MVP, MCSA, MCDBA, MCTS, MCITP

  2. Why we consolidate • Reduce server count • Reduce Cooling Costs • Reduce Power Costs • Reduce license costs • Take advantage of faster servers

  3. Consolidation Options • Multiple Databases in a single instance • Multiple Instances on a single server • Multiple virtual servers into one physical server

  4. Multiple Databases 1 Instance • Saves on License Costs • Saves on Hardware Costs • Shared Buffer Cache • Shared Procedure Cache • Shared CPUs • No control of buffer/proc cache size

  5. Multiple Instances 1 Server • Save on License Costs • Save on Hardware Costs • Separate Buffer Cache • Separate Procedure Cache • Shared or Isolated CPUs • Influence buffer/proc cache sizes via max memory

  6. Multiple virtual servers 1 host • Save on Hardware Costs • Can save on License costs • Separate Buffer Cache • Separate Procedure Cache • Shared or Isolated CPUs • Control of cache size by controlling VM resources

  7. How to select a technique • CPU Load • Buffer Cache Size • Procedure Cache Size • Page Life Expectancy • Disk IO Load • Legacy Server CPU & RAM

  8. When is it not going to work • All servers have high CPU Loads • All servers have large buffer cache requirements • One or more servers have large procedure cache requirements • JBOD can’t handle the IO • Single Server can’t handle the RAM

  9. More Reading • When and How to Consolidate • http://bit.ly/bFx8il • Server Consolidation with SQL Server 2008 (MS) • http://bit.ly/catkb2 • SQL Server Consolidation on the 64-Bit Platform (TechNet) • http://bit.ly/90Ql4M

  10. Can I really consolidate my SQL Server database? Denny Cherry dcherry@awarenesstech.com http://itke.techtarget.com/sql-server Please rate this presentation at http://speakerrate.com/mrdenny

More Related