Measure tables per filegroup from allocation metadata, include LOB and overflow pages, and separate partition placement from growth history.
Data Lake vs Data Warehouse: What Each One Is For
Data Lake vs Data Warehouse is a choice between raw files and cleaned, modeled tables. This post compares schema on read with schema on write, who uses each, and why many teams combine them in a lakehouse.
Read-Only Filegroups: Locking Away Old Data
Read-only filegroups let you lock old data so nothing can change it by accident. This post moves old rows to their own filegroup, makes it read-only, shows what still works and what fails, and explains how partial backups skip the locked data.
Pages and Extents: How SQL Server Stores Rows in a Data File
Pages and Extents are the building blocks of every SQL Server data file. A page is 8 KB, an extent is eight pages, and a row has to fit on a page. This post shows how to count the pages a table uses and what happens when a row is too wide.
Rows, Columns and Tables: How a Database Holds Information
Rows, Columns and Tables are the three ideas behind every relational database. A table holds one kind of thing, a column describes one fact about it, and a row records one item. This post builds a small Books table in SQL Server and reads it back by row and by column.
Readable File Sizes: Converting Bytes to KB, MB and GB
Turn raw bytes into friendly sizes without losing accuracy. Includes the overflow trap and the 500 GB drive that shows as 465.7.
What Are Filegroups in SQL Server and When to Use Them
What are filegroups in SQL Server? A filegroup is a named container for data files, and an ordinary table or index lives in exactly one. This post builds a small demo, shows where a table lands, and gives honest advice on when extra filegroups help and when they only add work.