Platform
Database migration assessment
Datalobe inventories your source database through a read-only user, lists every finding by issue code, scores readiness and risk, and estimates effort.
214
findings across 42 issue codes
Readiness
Ready with remediation, 71/100
Risk
58/100, medium
Inventory of ERP-Oracle (Oracle Database 19c)
- Schemas
- 5
- Tables in scope
- 1,036
- Rows
- 2,141,876,402
- Size
- 412 GB
- Columns
- 71,940
- Code objects
- 540
214 findings across 42 issue codes
What it covers
What does the assessment cover?
The assessment covers six things you need to know before anyone writes a migration plan.
Inventory
Schemas, tables, rows, sizes, columns, constraints, indexes, sequences and code objects, minus backups and temporary tables.Findings by issue code
Each incompatibility becomes a finding with an issue code and affected objects, such as DFLUX-301, CONNECT BY hierarchical queries.Decisions
Some findings are choices, not technical problems. Example run: NUMBER without precision on 1,284 columns needed a decision.Manual work
Flags objects likely to need manual work, 10 in the example run, so a named engineer can plan for them.Readiness and risk
Two scores summarise the findings. Example run: ready with remediation, 71/100, and risk 58/100, medium.Effort estimate
Hours split across schema and code, data and validation. Treat it as a planning figure, not a quote.
How it works
How does the assessment work?
Four steps, from a read-only connection to a scored, estimated report.
1. Connect read-only
Give Datalobe a read-only user that can read data and the system catalogue, or send a schema export.
- User DFLUX_RO
- Read-only
2. Build the inventory
Datalobe lists what is in scope. Exclusion patterns leave out backups and temporary tables.
- 1,036 tables
- 540 code objects
3. Find what will not move as is
Each incompatibility becomes a finding with an issue code, the objects it affects and how it will be handled.
- DFLUX-301
- 214 findings
4. Score and estimate
Readiness and risk scores summarise the findings, and the effort estimate splits the hours.
- Readiness 71/100
- 840 h
Report
What does the Assessment Report show?
The report from the example run on ERP-Oracle (Oracle Database 19c), section by section.
| Section | Example result |
|---|---|
| Scope | 1,112 tables found, 76 excluded (2.1 GB), 1,036 in scope |
| Size | 2,141,876,402 rows, 412 GB, 38 partitioned tables |
| Constraints and indexes | 7,969 constraints, 4,212 indexes, 688 sequences |
| Code objects | 540: 212 procedures, 96 functions, 24 packages, 88 triggers, 120 views |
| Readiness | Ready with remediation, 71/100 |
| Risk | 58/100, medium |
| Findings | 214 findings across 42 issue codes |
| Effort | 840 h: schema and code 640 h, data 120 h, validation 80 h |
Related
Related features
- Stored procedure conversionThe next step for the code objects in the inventory.
- Data migration validationHow the migrated database is checked against the source.
- Cloud or self-hosted deploymentDatalobe Cloud, or self-hosted, single-tenant, on request.
Questions
Frequently asked questions
What access does the assessment need?
A read-only database user that can read data and the system catalogue, or a schema export. The website never asks for database passwords; connection details are handled inside the product.
How is the effort estimate calculated?
It is built from the findings and the inventory, split into schema and code, data, and validation hours. Example run, demo data: 840 h in total, 640 h, 120 h and 80 h.
Does the assessment change anything on the source database?
No. Datalobe uses a read-only user and needs no write access to the source.
Can we get an assessment before we buy?
Yes. The free database migration assessment gives you an Assessment Report on your own schema.
Free assessment
Get an assessment of your database
Send a read-only connection or a schema export and receive an Assessment Report.