-
Course
- Data
SQL Server: Why Physical Database Design Matters
This course shows how you to choose the right data types applicable to SQL Server developers and anyone who is responsible for designing and creating SQL Server tables and indexes, from SQL Server 2005 onward
What you'll learn
This course is about how your database’s physical design either takes advantage of or is hindered by the way that the SQL Server platform works; knowing this can give you better long-term scalability, availability, and performance. Choosing the right data types when you're designing your columns, tables, and indexes is really critical. Using the wrong data type can cause more space to be required, affecting data density in memory, database and backup size, transaction log efficiency, and more. It's even more important when you're choosing your clustering keys, as the wrong choice there can cause nonclustered index sizes to balloon dramatically. It can even affect the performance of queries, when incompatible data types are used in comparisons and cause very costly operations to take place. This course will show you how to make the right choices and avoid all of these problems. It starts by explaining the various data structures that are used to store columns and rows, and how they can be affected by data type choice. Then it shows how data type choice factors into clustered and nonclustered index key choice. Finally it describes the implicit conversion and probe residual problems that can occur from mismatched data types used in queries. Packed with a wealth of information and practical, easy-to-follow demonstrations, this course will show you how to make the RIGHT choices to make sure you avoid all these common problems. The course is applicable for all SQL Server versions from SQL Server 2005 onward, and for SQL Server developers and anyone responsible for designing and creating SQL Server tables and indexes, with any level of experience.
Table of contents
- Does Physical Database Design Matter? | 3m 42s
- Why is This Course Important? | 2m 16s
- What Does Physical Database Design Mean? | 5m 14s
- Prototyping Makes Perfect | 4m 24s
- Why is This Course Relevant? | 2m 35s
- Why Can I Teach This Course? | 3m 9s
- Course Focus and Structure (1) | 1m 57s
- Course Focus and Structure (2) | 2m 44s
- Introduction | 4m 53s
- It is Not Just About That Single Column Value | 2m 48s
- Use Common Sense: Do Not Take it Too Far... | 3m 11s
- Column Size and Number of Columns | 2m 14s
- Understanding Rows, Pages, and Storage | 2m 36s
- Data Storage Structure: IN_ROW_DATA | 4m 19s
- Data Storage Structure: ROW_OVERFLOW_DATA | 3m 52s
- Data Storage Structure: LOB_DATA | 3m 31s
- Record Structure | 4m 59s
- Demo: Analyzing Table Structures | 9m 19s
- Demo: Secondary Errors - Insert Error from Poor Column Choice | 4m 5s
- Record Structure: Key Points (1) | 2m 26s
- Record Structure: Key Points (2) | 2m 48s
- Vertical Partitioning (Limited LOB And LOB) | 2m 50s
- Vertical Partitioning: Customer Table | 4m 53s
- Vertical Partitioning Strategies | 2m 14s
- Record Structure and Compression | 3m 14s
- Summary: Column Size and Row Size Matter! | 1m 37s
About the author
Kimberly is a SQL Server MVP, Microsoft Regional Director and President/Founder of SQLskills.com, which she now runs with her husband, Paul Randal. Kimberly’s areas of expertise focus on performance tuning through effective database design and architecture.
More Courses by Kimberly