Let me show you why data types still matter
summary
Demonstrates concrete failures from mismatched types: float rounding causes comparisons to evaluate false even though SSMS prints 0.3, and NVARCHAR uses two bytes per character so concatenation with VARCHAR can silently truncate strings. Shows a real rescue: changing column types shrinks a table from terabytes to megabytes (from ~2.2 TB to ~200 MB while row count falls massively), fixes partition elimination by matching datetime precisions and cuts an ETL from 12 hours to under 2, and exposes costly implicit conversions and huge memory grant requests (tens of GB).
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:52Float data type surprises
- 4:45Dangers of float for precision
- 5:07String concatenation issues
- 7:39Unicode vs non-Unicode strings
- 8:24Choosing string column types
- 10:13Data types and performance
- 12:00Memory grants and data types
- 12:20Partition elimination precision
- 15:34Implicit conversion costs
- 18:00Questions and closing remarks
related talks
19mLet me show you why data types still matter- 19mLet me show you why data types still matter
19mNO ARRAY OF SUNSHINE: an introduction to data types from a data quality perspective
54mLessons learned from refactoring multi terabyte databases for the last 10 years
52mWriting T-SQL code for the engine, not for you "more demos" by popular demand
48mMS SQL New functions, syntaxes, tips & tricks
59mLessons Learned from the Trenches: Connectivity and Performance Tips&Tricks
53mThe Most Important Performance Factor in SQL Server and Azure SQL