4 extreme performance - part ii


Published on

Published in: 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
  • 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.
  • 4 extreme performance - part ii

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