Presentation on theme: "Microsoft SQL Server Architecture"— Presentation transcript:
1Microsoft SQL Server Architecture Tom Hamilton – America’s Channel Database CSE
2Common SQL Server Versions Product OverviewSQL Server 2008SQL Server 2012
3SQL Server Components Databases Database Files and File Groups Transaction LogsBackup and RecoveryMicrosoft ClustersProtocolsDisaster Recovery
4SQL Server Databases System databases User databases Master Model MSDB ResourceTempdbUser databases
5SQL Server Files Binaries Datafiles (.mdf, .ndf) Transaction log files (.ldf)Backup files and snapshot filesFile groups
6SQL Server 2005 New Feature: Data Partitioning Using File Groups Resources:
7SQL Server Transaction Log When the end of the logical log reaches the end of the physical log file, the new log records wrap around to the start of the physical log file.
8SQL Server Recovery Model Architectures Three Models:Simple: Truncate occurs on checkpoint (default in SQL2000)No “roll-forward” capabilityData loss acceptableBulk Logged: All operations are logged except bulk operations (BCP, BULK, etc) (DSS environments)Roll forward capabilitySome data loss acceptableFull: All ops are logged (Default for SQL Server 2005)Full roll forward/backLeast amount of data loss possible
9SQL Server Recovery Model Architectures DescriptionWork Loss ExposureRecover to point in time?SimpleNo log backupsChanges since the most recent backup are unprotectedCan recover only to the end of a backupFullRequires log backupsNormally noneCan recover to a specific point in timeBulk loggedIf the log is damaged or bulk-logged operations occurred since the most recent log backup, changes since the last backup must be redonePoint in time is not supported
10SQL Server 2005 New Feature: DB Snapshots – Copy on write Key Points from SQL Books Online (BOL)Intended for reporting to a point in time at mirror site or locallyPerformance is reduced due to increased I/O on the source database resulting from a copy-on-write operation to the snapshot every time a page is updated.Snapshots of the model, master, and temp databases are prohibited.Specifications of the database snapshot files cannot be changed.Files cannot be dropped from a snapshot.Can’t backup or restore snapshots.Can’t attach or detach snapshots.Can’t clone a snapshot.Before reverting a database, consider the following:
11Microsoft Cluster Server Implementation ConsiderationsHardwareSoftwareNetwork
13SQL Server 2005 New Feature: DB Mirroring Database FailoverVery fast failover – less than 3 secondsAutomatic or manual failoverWorks with dissimilar hardware and storageSync and async modes supportedMore info:This is a great solution but will not be released until a later service pack.Key points:First, explain principal and mirror and witnessRelationships can be bidirectionalCustomer view:
15Microsoft SQL Server Mirror Vs. SnapMirror Data transfers Licenses Server-server vs. controller-controller Reversible sync Failover Database only vs. everything Go for win-win
16New in SQL Server 2012 Availability Groups SMB SMB
17SQL Server Replication Transactional ReplicationMerge ReplicationSnapshot replicationReplication is a set of technologies for copying and distributing data and database objects from one database to another and then synchronizing between databases to maintain consistency. Using replication, you can distribute data to different locations and to remote or mobile users over local and wide area networks, dial-up connections, wireless connections, and the Internet.Transactional replication is typically used in server-to-server scenarios that require high throughput, including: improving scalability and availability; data warehousing and reporting; integrating data from multiple sites; integrating heterogeneous data; and offloading batch processing.Merge replication is primarily designed for mobile applications or distributed server applications that have possible data conflicts. Common scenarios include: exchanging data with mobile users; consumer point of sale (POS) applications; and integration of data from multiple sites.Snapshot replication is used to provide the initial data set for transactional and merge replication; it can also be used when complete refreshes of data are appropriate. With these three types of replication, SQL Server provides a powerful and flexible system for synchronizing data across your enterprise.