Your SlideShare is downloading. ×
4   extreme performance - part ii
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

4 extreme performance - part ii

598
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
598
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Complex event processing involves the processing and querying of data when the data is in flight. The data needs to be processed before there is time to persist it.Such processing involves very high data rates and often deals with multiple concurrent event sources and multiple output data.The aim is to process with as little latency as possible.
  • Slide ObjectiveSQL Server “Denali” AlwaysOn can give you many advantages, including the ability to failover entire applications, easier setup, multiple failover targets, and remote failover.Speaker ScriptSQL Server “Denali” makes high availability and disaster recovery much easier to set up and maintain. With the new availability groups, you can:Have a database and dependent objects fail over as a unit, so you do not have to manually duplicate changes from the master server to the failover servers. This decreases the effort to maintain the system and increases uptime.Provide faster failover for reduced downtime. Failover now is in the order of one minute, down from multiple minutes.Define a failover policy so you can fail to different servers. This lets you reduce the amount of hardware that is sitting idle waiting for a server to fail as well as providing options for local and remote failover.Provide up to four secondary servers. Two are synchronous servers (up-to-date mirroring), with the others being asynchronous (some latency with log shipping).In addition, many operations that used to lock users out of the server now can be performed online, so you do not have to schedule as many maintenance windows.Finally, with support for running SQL Server “Denali” on Windows Server Core, you can reduce the number of operating system patches to increase data availability.
  • Transcript

    • 1. Scaling out
    • 2. Scalable Shared Databases
    • 3. SQL Server’s greatest challenge
      • We want availability and scalability!
      • 4. The database is a single point of failure
      • 5. The database is the performance bottleneck
      Scale Out
      Scale Up
    • 6. A DBA’s dream
      • Application/website always online
      • 7. Workload is distributed amongst many servers
    • Replication: How does it work?
    • 8. Peer-to-Peer Replication
      • Databases replicate reciprocally and are writable
      • 9. Redundancy provides fault tolerance and lowers maintenance downtime
      • 10. Online upgrades possible
    • Peer-to-Peer Topology
      Logreader
      Agent
      Logreader
      Agent
      Logreader
      Agent
      Dist
      DB
      Dist
      DB
      Dist
      DB
      Distribution
      Agent
      Distribution
      Agent
      Distribution
      Agent
      Los Angeles
      London
      Transactional
      Replication
      Taipei
    • 11. P2P - Common scenarios
      Scale out reads and writes
      or…
      Scale out reads, but writes are done to one node only
    • 12. Peer-to-Peer Replication
    • 13. Multisite solution?
    • 14. Back to the DBA’s dream
      Application/website always online
      Workload is distributed
      Implementing
      Peer-to-Peer
    • 15. Challenges
      • Design your schema and topology properly to prevent conflicts
      • 16. P2P is an asynchronous solution and does not guarantee zero data loss or zero latency
      • 17. Not completely transparent
      • 18. Although transparent enough!
    • New features in 2008 / R2
      Online topology changes
      Conflict detection
      Partition switch support
      Performance improvements
      Snapshot delivery of more than 500MB/minute
      One of the interesting benchmarks for a pull subscriber, time to deliver 100,000 varbinary (max) records:
      Win2003/SQL2005 – 223 minutes
      Win2008/SQL2008 – less than 2 minutes!
    • 19. Conclusion: Peer-to-Peer
      Peer-to-Peer Replication is one of the best methods for systems scale out
      Dramatically increase performance
      Eliminate downtime
      SQL Server 2008 provides major improvements for Peer-to-Peer Replication, and makes it accessible and more robust
    • 20. Denali HADR
      Denali offers a brand new HADR feature
      High-availability and disaster recovery feature, using up to 4 replicas
      Replicas can be synchronous or asynchronous
      CTP1 supports only single
      asynchronous replica, CTP3 to be released shortly
    • 21. SQL Server “Denali” AlwaysOn
      • Faster failover, easier administration with Availability Groups
      • 22. Identify databases to failover as a unit to reduce unplanned downtime
      • 23. Faster application failover using virtual name
      • 24. Increase application uptime using flexible failover policy
      • 25. Enable better data redundancy and protection with up to four secondaries and up to two synchronous secondaries
      • 26. Limited downtime with enhanced online operations
      • 27. Run Microsoft SQL Server® on Windows Server® Core to reduce planned downtime (50-60% fewer OS patch reboots)
      Shared Storage
      A
      A
      A
      A
      A
      A
      A
      Non-Shared Storage
      A
      A
      Disaster Recovery
    • 28. P2P
      Read-Write
      Up to 10 nodes
      Can replicate portions of the DB
      No automatic failover
      Although can be done through DNS
      2005/2008/R2/2011
      HADR
      Read only
      Up to 4 replicas
      Entire DB only
      Automatic failover
      2011 only
      Peer-to-Peer Vs. HADR
    • 29. יישמו את הפיצ'רים והטכנולוגיות שראינו היום אצלכם בארגון
      נצלו יכולות מחוץ ל"קופסה" של בסיס הנתונים
      בסיס הנתונים שלכם יעבוד מהר מדי פעם!
      סיכום