DataSZNYour data was dormant. Now it's in season.

Independent database engineering

Most companies cannot name the databases they are running.

I build a complete list of every database your company runs, who owns it, and which business application depends on it. Then I keep it current, so you know what is about to break before a user does.

Starts with a 3 to 4 week audit. You keep the inventory, the risk list, and the code to rerun it.

Estate inventory illustration

240
instances identified and mapped
Unidentified SQL Server Oracle PostgreSQL Db2
Typical mid-size estate. Every cell is a live database instance. Before: no owner, no engine, no inventory.

You already know if this is you.

None of these are unusual. They are what happens when a database estate grows faster than anyone's ability to document it.

Nobody can answer "what runs on this server?"

Monitoring shows hostnames. Hostnames mean nothing to the people who approve budgets, sign off on migrations, or decide what can be taken down on a Saturday.

Your inventory lives in a spreadsheet one person maintains

It was accurate the week it was written. Now it is a liability that gets cited in audits and quietly disbelieved by everyone who uses it.

Each engine has its own tool, its own owner, its own truth

SQL Server is watched one way, Oracle another, Postgres barely at all. No one view answers a question that spans them, so nobody asks questions that span them.

Certificates, patches, and end-of-life dates surprise you

Expiry is knowable months ahead. It becomes an incident only because nothing was watching the calendar across the whole estate.

You lost the person who knew

The knowledge was real. It was just never written down anywhere a second person could reach.

What actually makes someone call.

Nobody wakes up wanting a database inventory. Something forces the question. These are the six situations that bring people here, and where each one starts.

"We have an audit in ninety days and we cannot produce a list of our databases."

Estate AuditI produce the inventory, the application and owner mapping, and the version and end-of-life position as documents an auditor will accept, along with the queries that regenerate them next cycle so you are not starting over next year.

"Our DBA left and took everything with them."

Estate AuditI rebuild the picture from what the systems can tell me rather than what the person knew: directory services, backup job definitions, endpoint management, cloud APIs, and network flows. The result is written down where the next person can find it.

"We just acquired a company and we do not know what we bought."

Estate AuditFull discovery of the acquired environment: what is running, who owns it, and what is out of support. Usually the first honest answer anyone gives about integration cost.

"An executive asked which applications are at risk and nobody could answer."

Estate Audit, then DBMonitorThe audit ties every instance to the business application that depends on it. DBMonitor keeps it tied as the estate changes, so risk, migration progress, and outage impact can be reported in language the business already uses instead of hostnames.

"We are moving to the cloud and nobody agrees on what moves first."

Migration Dependency MapYou decide which applications move first. I tie each one to the instances and hosts underneath it, and show you where one server carries applications from different waves before that becomes a surprise on migration night.

"Something broke and it turned out to be a database nobody knew existed."

Estate AuditFinding the instances no tool is watching: departmental installs, developer machines running production workloads, forgotten cloud instances still being billed. This is nearly always the largest surprise in the first engagement.

What your team opens in the morning.

Each of those calls ends at the same place: one screen that answers the question. This is the order someone actually uses them. See the estate, find the problem, fix the record, check the collectors.

1 of 5 Estate overview
Every instance across four engines, counted two minutes ago. Ten open items, and the one that needs action today sits at the top.
Search a server name and land on the application it serves. Every host behind it, with patch level, certificate expiry, and status side by side.
Live and staged certificates compared alias by alias, so a name that dropped off the replacement is caught before the swap, not after.
When the registry says one thing and an engineer says another, the conflict is shown, not hidden. Every decision carries a name and a timestamp.
Every collector run, phase by phase, with the error when one fails. A collector that has gone quiet is marked stale, not trusted.

Illustrative data throughout. Select a screen to see it full size.Tap a screen to see the whole thing.

How an engagement runs.

Start with one piece of fixed work. Build only the modules that earn their place. Keep them true on a retainer. You can stop at any stage. This is estate work, not database administration.

  1. 1 Start Fixed fee, a few weeks Estate Audit or Migration Dependency Map. Find out where you stand.
  2. 2 Build One module at a time DBMonitor first, then only the modules that earn their place.
  3. 3 Keep Monthly retainer Estate Steward. The picture stays accurate as the estate changes.
1

Start

One-off, fixed scope. A clear picture of where you stand.

Estate Audit

What you are running, and who owns it 3 to 4 weeks, fixed fee

A complete, verified inventory of every database instance you are running, across every engine, with an owner and a business application attached to each one. I connect to what exists, reconcile it against whatever registry or CMDB you already have, and surface the gap.

  • Instance inventory across all engines, with version and patch level
  • Application and owner mapping for every instance
  • Drift report: what your registry says versus what is actually running
  • End-of-life and certificate expiry calendar
  • Ranked risk list with the three things to fix first

The document your team has been meaning to write for three years, plus the queries to regenerate it next quarter.

Migration Dependency Map

What has to move together 4 to 6 weeks

For cloud moves, datacenter exits, and consolidation. You decide which applications move first. I map every application to the database instances and hosts underneath it, and give you a move list per wave. Where one instance serves applications in different waves, you see the conflict before the move, not during it.

A per-wave move list at the host level. Sizing, cutover, and rollback stay with your team or migration partner.

2

Build

One module at a time. Monitoring that keeps the picture true.

The audit tells you where you stand once. The modules keep it true. DBMonitor comes first because it carries the platform: the collectors, the warehouse layers, the interface, and alerting on the collectors themselves. Every module after it is its own engagement, scoped and priced on its own. You commit to the first rung, not the whole ladder.

It runs on your infrastructure, against your databases, with no per-instance licensing and no vendor between you and your own inventory. I work as a consultant on your DBA team, so collection runs on access your team already controls. Each module ends with documentation and handover sessions, and your team owns the code when I leave.

DBMonitor

Inventory, status, and ownership 6 to 8 weeks foundation, required first

What you have, what is running, and what it belongs to. Discovery across every source that knows about a database, reconciled into one inventory, with current state visible per instance and per application. Includes the triage workbench for what rules cannot decide, and health checks on every collector run.

An inventory that stays true without anyone maintaining a spreadsheet.

See it: Estate Applications Triage Collectors

DBVersion

Versions and support status 3 to 4 weeks requires DBMonitor

Edition, version, patch level, and support status for every instance, tracked over time rather than sampled once. Every patch produces a new build string. Each one is classified once through the triage layer, then rolls up to product and version for good.

A lifecycle position you can take into a lifecycle review or a vendor negotiation.

DBPermissions

Who can access what scoped after DBMonitor requires DBMonitor

Logins, roles, elevated rights, orphaned accounts, and the privilege drift that has accumulated since the last time anyone looked. A directory services collector shows who is really behind each group login. Scoped once DBMonitor shows what is there, because it depends heavily on how your estate is run.

An access audit that regenerates itself instead of being rebuilt every cycle.

DBCerts

Certificate expiry scoped after DBMonitor requires DBMonitor

Certificates per instance with issuer, expiry, and owner, watched against a calendar and your change windows. Live and staged certificates are compared, so a missing name is caught before the swap. Scoped once DBMonitor shows what is there.

A dated expiry calendar with an owner attached to every entry.

See it: Certificates

Collectors

More sources, same inventory scoped per source alongside any module

Every organization runs different systems that know something about its databases: directory services, activity monitoring, infrastructure platforms, alerting tools, CMDBs, and application registries. A collector pulls one of those sources into the same model. Which ones you need is decided after I see what you run.

One more system feeding the same inventory, instead of one more tool to check.

3

Keep

Monthly retainer. Your DBAs run your databases. I keep the picture of them accurate.

Estate Steward

Keeping the modules running monthly, ongoing

A set number of hours each month to keep collectors healthy, work the triage queue, and extend coverage as your estate changes.

  • Standing weekly call and a prioritized backlog
  • Collector health, failures, and follow-up
  • Triage queue: unregistered instances, owner conflicts, version classification
  • New collectors and sources as the estate changes
  • Monthly estate report in application terms

What you are actually buying

The deliverable is a document. The value is what becomes possible once it exists.

Decisions stop waiting on one person

Migration scope, outage windows, and change approvals currently depend on whoever remembers. Written inventory moves that into something a team can act on without a meeting.

Risk gets stated in business terms

"Fourteen unsupported instances" is a number nobody can act on. "Payroll and Claims Intake run on unsupported versions" gets funded.

Audits stop being projects

The evidence an auditor asks for is the same evidence every year. Generated once and regenerated on demand, it stops consuming a quarter of someone's time each cycle.

Forgotten instances surface

Most estates carry instances nobody uses and hosts nobody claims. Once they are on a list with an owner column, deciding what to do about them stops being guesswork.

Surprises move earlier

Expiry dates, capacity limits, and support windows are all knowable months ahead. They become incidents only because nothing was watching.

You own what I build

Code, queries, schema, and documentation stay with you. No per-instance licensing, no platform to renew, no dependency on me after handover.

Raw capture and published truth are not the same layer.

Most internal dashboards fail because collection, cleaning, and presentation happen in one place. When a number looks wrong, nobody can tell whether the database is broken or the report is. I keep them apart: five stages the data moves through, and four layers that govern it. A boundary you cannot point at is not a boundary.

  1. 1

    Capture

    Raw results land exactly as each source returned them. Nothing is edited.

  2. 2

    Model

    Four engines' output becomes comparable facts, one grain each.

  3. 3

    Relate

    Hostnames are linked to applications and owners, here and nowhere else.

  4. 4

    Publish

    Joined views a report can read. The contract never breaks without notice.

  5. 5

    Serve

    Timestamped snapshots, so screens load fast and show their age.

Across every stage

  • Govern

    Rules suggest, engineers decide, and every entry names who made it.

  • History

    Append only. Nothing is rewritten.

  • Access

    Nobody sees what their role does not grant.

  • Health

    Every collector run is recorded. Silence is a failure.

Twelve years of this, at production scale, under regulation.

I spent twelve years as a SQL Server administrator before I built any monitoring, which is the reason my monitoring works. Observability designed by people who have never been paged at three in the morning measures the wrong things beautifully.

For the last five years that has been my day job, end to end: the collection layer, the warehouse model, the API, the interface, and the governance process around it. The estate runs past five hundred instances across four engines. The tooling is read daily by engineers and by executives who have never written a query.

The work that reached the leadership table was not the monitoring. It was the mapping: connecting raw infrastructure to the business applications that run on it, so that migration progress could be reported in terms of applications rather than server counts.

Twelve years deep in SQL Server. Mapped, modelled, and monitored across all four.

SQL Server Oracle PostgreSQL Db2
12
years administering production SQL Server
500+
instances in the estate I work across daily
4
engines mapped and monitored side by side

You are hiring a person, not an agency.

I am Zeeshan. DataSZN is me. When you book a call you talk to the engineer who will do the work, and when the project ships there is no account manager between you and the person who wrote it.

That is a deliberate limit on how much work I take. I run one or two engagements at a time. If the calendar is full I will tell you that on the first call rather than staffing it with someone else.

My background is banking, which means regulated change control, audit evidence, least-privilege access models, and the assumption that anything I build will be reviewed by someone whose job is to find the problem with it. That habit travels well.

Zeeshan, the engineer behind DataSZN
  • SQL ServerTwelve years administering production SQL Server estates, hands on
  • Multi-engine estatesOracle, PostgreSQL, and Db2 mapped and monitored alongside SQL Server, schema through interface
  • Full stack of the problemPython and PowerShell collection, T-SQL and warehouse modeling, PHP and Vue interfaces
  • GovernanceLeast-privilege access frameworks with tiered approval, certificate and lifecycle tracking
  • CommunityActive in the SQL Server data community

Start with the audit.

Thirty minutes, no pitch deck. Tell me roughly how many databases you have and what made you start looking. I will tell you honestly whether this is worth paying for.

Good fit

  • +Twenty to a few hundred database instances
  • +More than one engine in play
  • +A DBA team busy running databases, with no time to map them
  • +An audit, migration, or acquisition forcing the question
  • +Willingness to act on what the inventory finds

Not a fit

  • −Under ten databases on a single managed service
  • −Looking for dashboards without fixing the data underneath
  • −Emergency incident response starting today
  • −Database administration: tuning, high availability, backup and recovery
  • −Analytics, BI, and executive reporting as the main goal
  • −Staff augmentation billed by the seat