You took over a system you did not build. An acquisition closed, or the last person walked out, or a reorg dropped someone else’s estate on your desk. Either way, you now own SQL Servers you cannot fully explain. That is the problem, and it is bigger than it feels on day one.
I have been in this seat. The handover document, if one exists, covers the three databases everyone talks about. It says nothing about the other eleven. Nobody can tell you which servers run backups, which backups have ever been restored, who has admin, or what breaks if a given box dies. The estate works today. That is the trap. Working today and recoverable tomorrow are two different facts, and you only inherited the first one.
Start with an inventory, not a deep dive. List every SQL Server instance, every database on it, the version, and whether it is in support. List who has admin on each. List the backup job and, separately, the last time anyone proved a restore worked. That second column is usually empty. An empty restore column is the line item that wakes you at 2:39am. A backup nobody has tested is a hope, not a recovery position.
Then rank by blast radius, not by age. The oldest server is rarely the scariest one. The scary one is the database with no documented owner that three production apps quietly depend on. Find those couplings before they find you. The dependency nobody mapped is a disaster that has not happened yet, sitting in plain sight, waiting for the first failure to introduce itself.
Here is the part to take upstairs. Inheriting an estate transfers the risk to your name whether or not anyone wrote that down. When something breaks at month-end on a box you did not know existed, the question is not who built it. The question is why the new owner did not know. Walk in with the inventory already done and that conversation goes a very different way.
The fastest way to draw the map is a free, read-only 15-minute health check. It touches nothing, changes nothing, and returns a graded plain-English report of what you actually inherited: versions out of support, who holds admin, where the recovery gaps are. Run it before the estate writes its own introduction at the worst possible hour. Book the check on sqldba.org.
Want to know if this is sitting in your estate? We run a read-only check and hand you a graded report in plain English.
Get your free health check