My next article for SQL Server Magazine is out now. I've decided that New Year is the time that most people discuss diets and databases don't have to be an exception.
I'm discussing one large client who had a database that really needed to be trimmed down. That involved a whole range of mechanisms and the outcome was great: major size reduction and significant performance improvement.
I've decided to discuss this across a series of articles, each covering part of the story about how the reductions were produced and the rationale for each.
You'll find part one here now: http://sqlmag.com/database-performance-tuning/data-tales-case-database-diet-part-1