About Hannah Vernon

I’m Hannah Vernon, a database reliability and performance specialist, SQL Server enthusiast, software developer, and lifelong technology investigator. I’ve spent more than two decades working with databases in production environments, primarily in the Microsoft SQL Server ecosystem.

I started SQLServerScience.com because I believe understanding why something works is considerably more valuable than simply knowing how to make it work.

A little about me

My professional career has centered on designing, administering, troubleshooting, and improving enterprise database environments. I’ve worked with SQL Server installations ranging from individual instances to large, geographically distributed environments supporting thousands of databases.

My experience includes high availability and disaster recovery, performance engineering, database security, infrastructure migrations, automation, and the less glamorous but critically important work of keeping production systems reliable.

I’ve worked extensively with SQL Server technologies including Always On Availability Groups, Distributed Availability Groups, Query Store, Extended Events, replication, SQL Server Agent, and the underlying storage and query-processing architecture.

I’m also a software developer. I enjoy building tools that solve practical problems for database professionals, particularly when an existing solution is unnecessarily complicated, expensive, or simply doesn’t do what I need.

Why SQL Server Science?

SQL Server is a remarkably sophisticated piece of software. After years of working with it, I’m still discovering things that surprise me.

Some of those discoveries come from investigating undocumented behaviour. Others come from taking a familiar feature apart and examining what actually happens underneath.

That’s what I enjoy writing about.

You’ll find articles covering:

  • SQL Server internals: Storage structures, data types, query processing, memory management, and undocumented engine behaviour.
  • Performance engineering: Execution plans, indexing, cardinality estimation, query optimization, and performance troubleshooting.
  • Database reliability: High availability, disaster recovery, backup and recovery, monitoring, and operational practices.
  • Security: Authentication, authorization, encryption, auditing, and the security implications of database architecture.
  • Development and automation: T-SQL, PowerShell, C#, source control, deployment practices, and tools for working DBAs.
  • The evolving DBA profession: Cloud platforms, artificial intelligence, automation, and the changing relationship between database professionals and the software they manage.

I particularly enjoy experiments that challenge conventional wisdom. If a claim about SQL Server sounds interesting, I’d rather build a test and find out whether it’s true than repeat something I’ve read elsewhere.

Research, not just repetition

I believe technical writing should be grounded in evidence.

Where practical, articles include reproducible scripts, execution plans, test results, screenshots, and references to Microsoft’s documentation. I try to distinguish documented behaviour from observed behaviour, and both from my own interpretation.

I also make a point of identifying limitations in my experiments. A result observed on one version of SQL Server, with one workload and one configuration, isn’t automatically a universal truth.

Some of my research has involved systematically examining SQL Server’s system catalogs across major releases, identifying undocumented objects and investigating how the database engine implements features beneath its public interfaces.

I’m particularly interested in the gap between what a product is documented to do and what it actually does.

That gap can be an excellent place to learn something.

Community and collaboration

I believe professional knowledge becomes more valuable when it’s shared.

I’m a moderator and long-standing contributor to Database Administrators Stack Exchange, where I’ve spent more than 14 years reviewing and curating community contributions, answering database questions with more than 1,300 published answers, and helping maintain a useful technical resource for the DBA community.

I’ve also published over 385 technical articles here on SQLServerScience.com, covering subjects ranging from foundational database concepts to obscure SQL Server internals.

My open-source work includes tools and projects intended to make database administration, monitoring, and troubleshooting more effective.

I’m particularly interested in helping other database professionals develop the confidence to investigate problems themselves, rather than relying exclusively on recipes and prepackaged answers.

A note about artificial intelligence

Artificial intelligence is changing software development and database administration, and I’m interested in understanding where it genuinely helps.

I experiment with AI coding agents and local language models, and write about their practical application to DBA work. I’m interested in both their capabilities and their limitations.

Some of my AI-related writing has been developed collaboratively with AI tools. Where that’s the case, I believe readers deserve transparency about the process.

Regardless of how an article begins, technical claims still need scrutiny. Plausible-sounding output isn’t evidence, and I don’t consider an AI-generated answer a substitute for understanding the technology.

The person behind the keyboard

Outside of databases, I enjoy photography, technology, networking, Linux, self-hosting, and generally finding interesting things to take apart and understand.

I have an enduring curiosity about how things work, particularly when the answer turns out to be more complicated than expected.

That curiosity is probably the single biggest reason this website exists.

Get in touch

If you’ve found an error in an article, have a different interpretation of an experiment, or have discovered something interesting about SQL Server, I’d genuinely like to hear about it.

Technical disagreement is welcome. In fact, it’s one of the best ways we learn.

You can find me on:

Thanks for reading. I hope you find something here that makes you a better database professional.