The document discusses new features in SQL Server 2012 related to performance, business intelligence (BI), and disaster recovery (DR). It focuses on enhancements to the database engine, analysis services, and AlwaysOn availability groups which allow for high availability and failover clustering across multiple SQL Server instances. The presentation includes demos and discussions of columnstore indexes, partition support, and other tools to improve scalability and performance.
Power Viewsemantic model - way of explaining relationship between doing different kinds of reporting in a meaningful way. Explain, rather than syntax. Diff mutlidimensional, and tabular report, how you use analysis server
Clustering: set of loosely connected computer that work together so that in many respects they can be viewed as a single systemMirroring: a mirror is an exact copy of a data set. Multiple source of the same informationLoad Balancing: a computer networking method to distribute workload across multiple nodesAvailability: The degree to which a system, subsystem, or equipment is in a specified operable and committable state Disaster Recovery: is the process, policies and procedures that are related to preparing for recovery or continuation of technology infrastructure which are vital to an organization Failover: is automatic switching to a redundant or standby
2008 R2 – single database – bad when have SharePointMirroring gave redundant copy so had a point of failure – the SANRemote data center require log shippingSaves servers, need disksRedundant copies – up to 4 – sync and async
Sync = commit, more expensive, but always in syncAysnc – will commit / eventually get there, but one site could be out of date.http://blogs.msdn.com/b/saponsqlserver/archive/2012/02/07/sql-server-2012-alwayson-what-is-it.aspxhttp://msdn.microsoft.com/en-us/library/ff877931.aspxThis is an basicallyCluster-Aware Updating (CAU), which is a feature for failover clusters in Windows Server 2012 that automates the updating process on clustered servers while maintaining high availability
Primary: active instance which handles the primary workload – read/writeSecondary:Are the instances which receive the transaction log records – read onlyAvailability group: Is the logical frame around one or more database and represents the unit of failoverPrimary replica – makes logsSecondary replica – receives logsAvailability replica – availability group hosted by sql server – has a singly primary replica, and 1-4 secondary replicas
Primary: active instance which handles the primary workload – read/writeSecondary:Are the instances which receive the transaction log records – read onlyAvailability group: Is the logical frame around one or more database and represents the unit of failoverPrimary replica – makes logsSecondary replica – receives logsAvailability replica – availability group hosted by sql server – has a singly primary replica, and 1-4 secondary replicas
Stretched vs failover
Speed of light – 1/ms about 200 miles in a vacum.Async somewhere else, and read/write issuesNot supported in 2013
For AOExplain domain, hardware, software, firewallExplain WFSC – checks and create – go over this pieceLook at nodes in WFSCLook at Mgmt studio – show node – say must be configured in configmgr on each serverCreate Availability groupCreate listenerShow Dashboard by right click alwy on HA – start failover wizard