"...interesting maps for the DBA to ponder on heavy OLTP database schemas..." There is a lot of work here, but what is the point? I'm a DBA who prefers to know as little as I need to know about bits and bytes, so I can concentrate on best modeling of business processes to database design. As the author states at the beginning of the article, some would argue that this look under the covers is not necessary. Meanwhile, is there garbage/redundant data in these tables that are moving around the disk space? Do the owners of the data understand all they have out there? Is there some data migrated from a legacy system that no user ever queries, that could be archived and deleted from the active database? Do you have a data dictionary and are you keeping it current? Are you more interested in the DBMS than the databases? Do you want to work for Microsoft on the SQL Server development team?