SQL Server: Myths and Misconceptions

Learn the truth about common SQL Server myths applicable from SQL Server 2005 onwards. There is so much information online about SQL Server, however much of it is inaccurate to some degree. In this course, you will learn the truth behind more than 80 myths and misconceptions about SQL Server that can cause you performance and availability problems – from someone who wrote the SQL Server code. This course is perfect for developers and DBAs who have been struggling to make sense of conflicting information about SQL Server. The information in the course applies to all versions from SQL Server 2005 onwards.

Table of content

Introduction

• Introduction
• Why is Some Information Incorrect?
• Why Does Incorrect Information Cause Problems
• Summary
• Course Structure

Performance Myths and Misconceptions

• Introduction
• Controlling Instant File Initialization
• Demo: Enabling Instant File Initialization
• Temporary Table Abuse
• Demo: Using Temporary Tables
• Tempdb Sizing
• Data Compression
• Data File Shrinking
• Demo: Effect of Data File Shrinking
• Updating Index Key Columns
• Demo: Updating Index Key Columns
• Snapshot Isolation
• Checkpoints
• NULL Bitmap
• Tempdb Data Files
• Solid State Disk Uses
• Disk Queue Length
• Page Life Expectancy Threshold
• NUMA Effect on Page Life Expectancy
• CXPACKET Waits
• ASYNC_NETWORK_IO Waits
• Demo: Wait Statistics
• Overriding MAXDOP

Transaction Log Myths and Misconceptions

• Introduction
• Log Truncation/Clearing
• Transaction Log Analysis
• Demo: Analyzing the Transaction Log
• TRUNCATE TABLE Logging
• Efficient Logging of Index Operations
• Demo: Showing Efficient Logging
• Multiple Log Files
• Instant File Initialization
• Transaction Log Sizing
• Log Record Removal
• Log Record Movement
• Using BULK_LOGGED to Reduce Log Backup Size
• Demo: Log Backup Size Using BULK_LOGGED
• Log Backup Size vs. Log Size
• Disaster Recovery and BULK_LOGGED
• Demo: Disaster Recovery and BULK_LOGGED

Indexing Myths and Misconceptions

• Introduction
• FILLFACTOR Usage
• Clustered Index Rebuilds
• Nonclustered Index Choice
• SSDs and Fragmentation
• Removing Heap Fragmentation
• GUIDs as a Cluster Key Choice
• Demo: GUID Cluster Keys
• Rebuilding Indexes and Statistics

Locking Myths and Misconceptions

• Introduction
• Online Index Operations and Blocking
• Demo: Locks held by Online Index Rebuild
• Backups and Blocking
• DBCC CHECKDB and Blocking
• Lock Escalation
• Demo: Lock Escalation
• Invalid Blocking and Deadlocks
• NOLOCK and READ UNCOMMITTED

Transact-SQL Myths and Misconceptions

• Introduction
• Nested Transactions
• Demo: Nested Transactions
• DDL Triggers
• SELECT COUNT(*)
• Demo: SELECT COUNT (*)
• Physical Record Location
• DEMO: Physical Record Location
• Running DMVs in 80 Compatibility Mode

Backup Myths and Misconceptions

• Introduction
• Concurrent Data and Log Backups
• Data Backups and Log Clearing
• Demo: When Does the Log Clear
• Backup Completion Guarantees
• Differential Backups
• Planning a Backup Strategy
• Restarting the Log Backup Chain
• Demo: Log Backup Chain
• Replacing Backups with Database Snapshots

Restore Myths and Misconceptions

• Introduction
• Mix-and-Match Filegroups
• Demo: Filegroup Restores
• Using WITH STOPAT for Data Backups
• Restoring to Older Versions of SQL Server
• Demo: Down-level Restore
• Restoring to Non-Enterprise Editions
• 32-Bit vs. 64-Bit Compatibility

Corruption Myths and Misconceptions

• Introduction
• Detaching and Attaching a SUSPECT Database
• Offloading Consistency Checks
• Causing Corruption Using T-SQL
• Enabling Page Checksums
• DBCC CHECKDB vs. BACKUP … WITH CHECKSUM
• Restarting SQL Server to Fix Corruption
• Disappearing Corruptions
• Corruption-Free Guarantee
• Repair Can Fix Everything
• Repairing System Databases/Tables
• Transaction Rollbacks
• Demo: Transaction Rollbacks

High-Availability Myths and Misconceptions

• Introduction
• Database Snapshot Size
• Database Snapshot Efficiency
• Demo: Database Snapshot Memory Usage
• Database Mirroring Failure Detection
• Database Mirroring Failover Speed
• Failover Clustering is the Best High-Availability Technology
• Multiple Database Mirors
• Transactions After a Failover
• Replication is a Valid High-Availability Choice

Rapidgator.net

1. http://bit.ly/1gHLW4G

Uploaded.net

1. http://ul.to/qlwhi9gm

 Cloudzer.net

1. http://clz.to/file/ikll5oec