Presentation is loading. Please wait.

Presentation is loading. Please wait.

Objectives Provide insight into how SQL Server is used in Mission Critical Environments Provide real-world customer engagements and design to meet.

Similar presentations


Presentation on theme: "Objectives Provide insight into how SQL Server is used in Mission Critical Environments Provide real-world customer engagements and design to meet."— Presentation transcript:

1

2

3

4 Objectives Provide insight into how SQL Server is used in Mission Critical Environments Provide real-world customer engagements and design to meet business critical needs with SQL Server Takeaways  SQL Server is used in Mission Critical Business Environments  SQL Server is Enterprise ready

5 “If this system is down our business suffers” “Failure is not an option” “We require 100% uptime for 32400 seconds each business day” “Each minute of downtime costs us money and customers” “Planned or unplanned system downtime is not acceptable to our business users or our customers.” “[We] operate assembly factories 24 hours a day, seven days a week”

6

7

8

9 SQL Server Environment 100+ SQL Server Instances 120+ TB of data 1,400+ Databases 1,600+ TB storage 450,000+ SQL Statements per second on a single server 500+ Billion database transactions per day Core component in solutions designated for: Financial transactions Gaming environments Tracking user state throughout the system Solutions primarily scale-up using commodity hardware

10 **SQL Server DBs

11

12

13 Application Session State is at the heart of BWin.party platform Controls user context as they move through the system Initial configuration able to handle approximately 15,000 users per SQL Server instance Scale-out 18 SQL Servers Latching lead to need to scale-out without fully utilizing system resources. Faster site and page loads would allow for more user bets and provide a better overall experience

14 Memory-Optimized TablesSize in Memory: ~20 GB Rows in largest tables: 5 million peak Durability: SCHEMA_ONLY Indexing: Mostly HASH indexes, with one nonclustered (range) index Natively Compiled ProceduresConversions Required: Migrated all to insert/update/delete to Natively Compiled InterOp: Used wrapper procedures for handling conflicts (to avoid client receiving error) and BLOB passing. Kept other parts as InterOp as no need to migrate as not the bottleneck Hardware4-socket blade. 60 Cores, HT disabled, 512 GB RAM, 900 GB HDD (SAS, RAID-1), 10 GB NIC Development timeInitial prototype implementation done in 2 days No application or web server code changes required In Production for almost 2 years

15

16

17

18 Company Profile Owns and operates: 3 clearing houses, 5 central securities depositories 26 markets with a combined value that exceeds US$8 trillion. In addition, Nasdaq's exchange technology, including trading, clearing, CSD and market surveillance systems, is in operation in over 100 marketplaces across USA, Europe, Asia, Australia, Africa and Middle East. Business critical to world financial markets operations Business Requirements Availability: Data must be 100% available during business day Performance: Is as critical as data availability. Handle a million trans/second with sub ms latency Managing large data volumes : Working with petabytes worth of data Established in 1971 as the world’s first electronic stock market

19

20

21 Project Description Maintains US Equities and Options trading data Processing 10’s of billions of transactions per day Average over 1 million business transactions/sec into SQL Server Peak: 10 million/sec Require last 7 years of online data Data is used to comply with government regulations Requirements for “real-time” query and analysis Approximately 500 TB per year, totaling over 2PB of uncompressed data Largest tables approaching 10TB (page compressed) in size Early Adopter and upgrade to SQL Server 2014 in-order-to: Better manage data growth Improve query performance Reduce database maintenance time

22 Data at this scale require breaking things down into manageable units: Separate data into different logical areas: A database per subject area (17) A database per subject area per year (last 7 years) Table and Index Partitioning: 255 partitions per database 25,000 filegroups Filegroup to partition alignment for easier management/less impact moving data Filegroup backups Taking advantage of compression: Compression per partition Backup compression

23 Space Savings: Compression savings: 2x-4x over page compressed 5-8x over uncompressed data Additional 2x with backup compression Archival compression testing provided 20% further compression

24 Load Performance: Eliminated need for index creation after data-load. Loading directly into Columnstore Better positioned to keep up with ever-increasing data volumes On Average 1.5x throughput in loading files. Insert-only via bulk API Query Performance: *More common Ease of migration: Transparent changes to end-user. No application code changes Greatly reduced maintenance and troubleshooting overhead. No need to do index maintenance such as defragment the index Type of QueryPage CompressedCCIGains Single Day5 seconds1 second5x History Report queries*16.5 min1.5 min12x

25

26

27

28 Purchase/Warehouse OF/ B2Bi Solution Business Process Modelling Workflow Supply Chain Management System E-Customs Warehouse Management Sales/Marketing Manufacturing Finance Management Computer Integrated Manufacturing Product Data Management Engineering Change Documentation MSS : Manufacturing Services Solution SQL Server ERP System Quanta ERP Architecture

29

30 To provide High Availability use SQL Server AlwaysOn Availability Groups (AGs) Synchronous mode to provide HA for DB tier Use Log Shipping for DR to remote site AlwaysOn AGs are handling peak workloads on Quanta SAP ERP system Hardware: 2 x HP DL980 1TB RAM FusionIO cards accelerate log write performance

31

32 CPU utilization: Avg <= 30% Peak 70%

33

34

35

36 Raw data reside in Azure Blob Storage Over 90 databases with multi-TBs of metadata Mix of Azure SQL Databases and SQL VMs Cold vs warm data SQL VMs have multiple AlwaysOn AG replicas

37 Each AlwaysOn replica has 20+ Datafiles on Blob Storage Utilize multiple storage accounts on Azure to maximize throughput Testing recently released Premium Storage to increase bandwidth and reduce latency

38

39

40

41

42

43  The results of the benchmark testing exceeded Temenos expectations  At peak performance, the system processed 11,500 transactions per second in online business testing  Averaged more than 10,000 interest accrual and capitalizations per second during close-of-business testing,  Processing 25 million capitalizations and account accruals in less than 42 minutes, with average database requests over 260,000/s.  Testing showed a near linear scalability of 95 percent as the number of agents increased  The performance results make the combination of T24 and Microsoft technologies a viable solution for the world’s largest banks Benchmark Results on SQL Server

44 SQL Server is used by many businesses, across geographical region and industry, to meet their Enterprise Mission Critical requirements SQL Server is used to handle some of the most demanding workload in the world SQL Server features such as: AlwaysOn Availability Groups and In-Memory technologies are utilized to meet challenging business needs around High Availability and Performance Businesses are utilizing SQL Server relational capabilities on premise, and in cloud(Azure) both with VMs and Azure SQL DB (PaaS) to meet their needs

45  Case Studies  BWin.party BWin.party  Nasdaq Nasdaq  Quanta Quanta  Service of Tax Administration Service of Tax Administration  Temenos Temenos

46

47


Download ppt "Objectives Provide insight into how SQL Server is used in Mission Critical Environments Provide real-world customer engagements and design to meet."

Similar presentations


Ads by Google