SQL Server Upgrade Request an assessment

Method

You should not find out on Saturday that the job failed.

A compatibility level, collation, or job step should be proven before production go-live. Software drafts the map and the tests; a named person signs them. We stand up an isolated replica (part of the engagement), then we can run the cutover, or your team can run the same tested runbook. The assessment is how intake starts.

Method

Four steps, through go-live if you want it

We rebuild the environment away from production, prove the path, then we can run go-live — or your team can, with the same artifacts.

  1. 01 · Intake

    Inventory and a secure drop

    NDA, instances, versions, jobs, and a transfer channel you control. No backups over email.

  2. 02 · Replica

    Isolated rebuild

    Schema and agreed artifacts are restored in a sandbox that is not production.

  3. 03 · Map and test

    STTM, lineage, then the move

    AI-assisted column map and lineage graph, dual-origin flags, human sign-off, then the upgrade or move in the replica — with tests tied to the map.

  4. 04 · Deliver

    Go-live, or a runbook

    We can execute production cutover from the tested path. Or we hand your team verified scripts, diffs, and a written go-live sequence. The SOW says which.

Accuracy before go-live

We do not move first and document later. In-scope columns get a source-to-target map. Lineage is a graph of how values flow. If a field can be produced more than one way, that is a decision — not a surprise in production. Those artifacts also support BCBS 239 evidence (accuracy, integrity, completeness) when you need them; we do not certify your programme. The methodology page lists the gates. The pipelines page lists patterns we will run.

Security and confidentiality

Customer backups and schema do not travel over email. Transfer is over a channel you control or a time-limited drop we give you. Artifacts stay isolated for the engagement and are removed when the work closes, unless you ask us to retain a copy under the SOW.

We do not publish customer names, hostnames, or schema. Proof on the website is anonymized until a customer agrees otherwise.

The assessment is how intake starts

Version, target, and timeline. We reply with a path — or a clear no. No public prices, no newsletter.

Request an assessment
Request an assessment