Microsoft SQL Server Flash Storage


Published on

Sumeet Bansal of Fusion-io defines a "Dream Database Architecture. You'll Learn:

* If Flash Storage is right for your organization
* How to set up for High Availability
* What's coming next in Solid State Storage

Lastly, you'll hear how software manufacturers are responding to the distributed architecture trend, including validation from leaders such as Microsoft and Oracle.

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Microsoft SQL Server Flash Storage

  1. 1. FLASH STORAGE FOR SQL SERVER Speaker: Sumeet Bansal Fusion‐io San Francisco SQL Server User Group San Francisco SQL Server User Group March 2011 Mark Ginnebaugh, User Group Leader,  Mark Ginnebaugh User Group Leader
  2. 2. Flash storage: Is it right for you? Sumeet Bansal Principal Solutions Architect, Fusion-io March 9, 2011 Microsoft Office San Francisco
  3. 3. Who am I? Until June 2009 • Vice President of IT & DBA at • Served at for a decade • Introduced Fusion-io at in Late 2008 Now • Principal Solutions Architect at Fusion-io • Evangelize through presentations, demos webinars etc presentations demos, • Help Clients discover ways of maximizing efficiency and performance and at the same time cutting costs • Still a huge fan of
  4. 4. Dream Database Architecture (DDA) DDA implies • High Performance • High Availability g y • Easy to Manage • Energy Efficient • Cost Effective
  5. 5. Dream Database Architecture (DDA) SAN ioMemory is core of DDA DRAM L1, L2 & L3 ioMemory CPU Cache N a n o s e c o n d (10E-9) ACCESS DELAY IN TIME M i l l i s e c o n d (10E-3)
  6. 6. What is possible – Metric Pre Fusion-io Post Fusion-io Improvement “Boost” Customer Facing Improvement Average duration of a 345 milliseconds 88 milliseconds 300% 4 Times Website pages faster, each page has SQL transaction multiple DB requests. Reducing Time fetching data improves customer experience, leads to better conversion. Time taken to take a full 2 hours 6 minutes 1900% 20 Times During backups, customer experience is backup of the largest no longer hindered. database Time taken to restore a 3 hours 15 minutes 1100% 12 Times Faster time to recovery, less loss full backup of the largest exposure in major downtime. database d t b Average number of 0.4 0.008 4900% 50 Times Less time for customer to wait on read/write operations another customers long running waiting in a queue to operation. complete Number of transactions 3011 163 1700% 18 Times Website pages faster, each page has in 1 hour window that multiple DB requests. Reducing Time took more than 500 fetching data improves customer milliseconds experience, leads to better conversion. More cart transactions per second.
  7. 7. What is possible - Wine.comBusiness Value Gained • 50x fewer average transactions in queue • Decreased Cart Abandonment and increased revenue by at least 2%. • Reduced daily backup window from 2 hrs down to 6 minutes • Gained extra revenue for a 2 hour duration every day of the year. • If avg. 2 hour revenue gained (off peak hours) is $2K, the total revenue gain per year is $730K • Year End invoices posted in a single day that used to take 1 month • Books closed faster than ever. • Zero database blocking with rollbacks • Saved considerable time in warehouse and finance with no lost inventory, duplicate inventory purchasing, and tedious research / reporting
  8. 8. Measuring performance on Fusion-io Try to measure application performance • Use profiler to track average SQL transaction completion time • Use perfmon to track various aspects: – Logical Disk:Disk Reads/sec (Read IOPS) – Logical Disk:Disk Writes/sec (Write IOPS) – Logical Disk:Disk Reads Bytes/sec (Read Throughput) – Logical Disk:Disk Writes Bytes/sec (Write Throughput) – Logical Disk:Avg Disk Sec/Read (Read Latency) – Logical Disk:Avg Disk Sec/Write (Write Latency) – Use the Physical disk object if need to track on disk level in a RAID configuration
  9. 9. Measuring performance on Fusion-io Following are some suggested tests on a non-production environment • Perform maintenance tasks like backup/restore/rebuild of indexes • Use multiple connections simultaneously to read or write to a table • Run most frequently executed stored procedures and time them • Measure latency in an active High Availability scenario like Database Mirroring
  10. 10. Addressing High Availability • Database Mirroring g • Synchronous • Asynchronous • Multi-site clustering Multi site • Requires Windows 2008 R2 • Requires a third-party data replication software – Data Keeper by Steel Eye Technologies – Double-take • SQL Server replication • Specific to certain environments • Works on Database Object level
  11. 11. Addressing High Availability • Neverfail • availability.html • Marathon • availability.html
  12. 12. Mirroring vs. ClusteringMirroring g Clustering g• Provides protection against data corruption • Does not protect against data corruption (page level corruption) because there are two because there is a single data store on the separate physical data stores. shared storage. • Starting from SQL Server 2008, the system g y • One has to either restore from a backupp automatically fixes corrupt pages (in or run a dbcc repair command with allow enterprise edition) for data loss option • Both options will result in data loss• Mirror failover can be completely automated using a witness server• Starting from SQL Server 2008, the transaction logs for mirroring are compressed before sending to the mirror. So much better network utilization
  13. 13. Mirroring vs. ClusteringMirroring g Clustering g• Ordinarily, the databases on the mirror server • Reading from a separate node, without are not readable. However, if enterprise impacting the primary is not possible edition is present, one can create read-only snapshots on the mirror server • The snapshot creation is a sub-second operation regardless of the size of the database • The snapshot can be dropped and recreated at an i t t d t interval ( l (say every 5 minutes) to keep up with the data • This helps to gain better value from the mirroring server
  14. 14. Mirroring really is better • Mirroring is fast • Mirroring allows for a distributed architecture • Shared storage is not really geared for performance, it is geared for capacity • A different architecture (Distributed) is needed to drive performance
  15. 15. Validation • IBM HP, and DELL are OEMs and expanding on relationships IBM, HP • Microsoft: SQL Server 2011 (Denali) • Will provide clustering options without requiring shared storage • There will be multiple mirrors per server possible • Oracle • Flashcache • Dataguard with complete automatic failover
  16. 16. Sneak Peek • DirectCache • Use ioMemory as cache • Automatic Data management • Increase performance and economize on existing SAN infrastructure • Will support Clustered environments too
  17. 17. DirectCache SAN DRAM L1, L2 & L3 ioMemory CPU Cache N a n o s e c o n d (10E-9) ACCESS DELAY IN TIME M i l l i s e c o n d (10E-3)
  18. 18. THANK YOU
  19. 19. To learn more or inquire about speaking opportunities, please contact: o ea o e o qu e about spea g oppo tu t es, p ease co tact: Mark Ginnebaugh, User Group Leader