Here is a claim you may not be able to answer cleanly. You do not know, today, which physical country holds every copy of your customer data. You know where your main system runs. You picked that region. You are less sure about the backups, the replica, the disaster-recovery copy, and the snapshot some migration left behind. Cloud regions ship with defaults. Backup and replication settings ship with defaults. Those defaults do not read your contracts.
This is how regulated data ends up offshore without a single decision being made. A new environment gets spun up. Someone accepts the suggested region. A geo-redundant backup option quietly mirrors your data to a second country to make it safer. Safer for availability, yes. Now you have personal or regulated records resting in a jurisdiction your privacy commitments and your client agreements never allowed. Nobody chose that. It just settled there, while everyone looked at uptime.
Can you say, without checking, that no copy of your data leaves New Zealand? If the honest answer is no, that is not a failure. It is the normal state of a system that grew faster than its paperwork. The risk is not the technical setting. The risk is the gap between what your contracts and your regulators were told and what is actually true on disk tonight.
Frame it the way a regulator or a large client will. Your privacy obligations and many commercial contracts care about where data is stored and processed, not about how clever your architecture is. A data-residency breach is not an outage. It is a finding. It surfaces in an audit, a client security questionnaire, or a complaint. At that point it is a contractual and reputational problem with your name on it, long after the engineer who accepted the default has moved on.
So two questions worth taking to the next board meeting. What would it cost, in lost contracts and regulatory attention, if a major client learned their data had been sitting in another country for years. And how would you find out, today, before they do. The answer is almost always written in the configuration already. It has been sitting there in plain sight. Someone just has to read it back.
We offer a free, read-only health check of your SQL Server estate. It takes about fifteen minutes, changes nothing, and returns a graded plain-English report you can hand to your board, including where your data and its copies actually live. No access to your systems beyond the read, no obligation, and no sales calls you did not ask for. If you cannot name the country your data sleeps in tonight, that is the report to start with.
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