India’s Leading Domain & Web Hosting Provider
Support
Domain & Login
Blog
Data and Database Assessment: A Target Engine for Every Instance
A data and database assessment inventories every database instance in an estate, engine, version, size, growth, licence, features used and connected applications, and recommends a target for each: managed database service, database on VMs, an engine change or retirement. NTSPL runs provider assessment tools and licence analysis so CIOs and CFOs see database cost and migration risk before waves are fixed.
Delivered on
In scope
Why Databases Decide Migration Risk and Licence Cost
Databases carry most of a migration's risk and a large share of its licence cost. A typical estate has SQL Server instances across four versions, a few Oracle databases on licences nobody has counted, MySQL and PostgreSQL copies built by developers, and file-based data in Access or FoxPro behind a finance process. Without an instance-level view, teams pick one target pattern for all and discover blocking features, collation issues or licence shortfalls during cutover.
NTSPL collects instance metadata and feature usage with provider assessment tools, reviews licence entitlements with procurement, and scores every instance for compatibility with managed services. Each instance gets a recommended target, managed service tier, database on VM, engine change candidate, consolidation or retirement, with blockers, size, change rate and expected cutover window, so database waves and licence purchases can be planned with evidence.
When an Instance-Level Database Review Is Needed
Signals you need Data & Database Assessment
- More than 20 database instances across two or more engines, with no inventory linking each to applications
- SQL Server 2012 or 2014 instances still in production after the end of extended support
- Oracle Enterprise Edition in use with processor licences tied to physical cores
- Databases above 2 TB or with change rates high enough to make cutover windows uncertain
When to choose something else
- You need an analytics target-state, data domains and platform strategy: that is a data strategy engagement, not a migration inventory.
- One or two databases with a confirmed target: go straight to migration design.
What We Record for Each Database
Instance inventory
Engine, edition, version, patch level, size, growth, collation, HA configuration and host for every instance.
Feature and compatibility scan
Use of features that block managed services, such as linked servers, CLR, cross-database queries, Oracle packages or file-system access.
Workload profile
CPU, memory, IOPS, log generation rate and peak windows to size targets and estimate cutover duration.
Licence position
Edition entitlements, Software Assurance, Oracle processor counts and support renewals, compared with target licensing rules.
Data sensitivity and dependencies
Personal or regulated data present, connected applications, ETL jobs and reporting consumers per database.
Instance Inventory to Target Selection Pipeline
Database Inventory to Target Engine Selection Pipeline
Assessment tools and DBA interviews build an instance inventory with feature usage and performance profiles. A rules engine plus licence analysis recommends a target per instance, which feeds database wave planning.
Select any component
Database Inventory to Target Engine Selection Pipeline: click any of its 7 components to see its role and the design choice NTSPL makes for it, or trace the 7-step primary path.
Database Assessment Tools on Each Cloud
Schema conversion assessment reports show how much Oracle or SQL Server code converts automatically to Aurora PostgreSQL or MySQL, which separates easy engine changes from hard ones.
The Azure Migrate SQL assessment rates each instance for SQL Managed Instance, SQL Database or SQL Server on VMs, and Hybrid Benefit is applied where Software Assurance exists.
Google's Database Migration Assessment tool profiles Oracle and SQL Server estates and estimates fit for Cloud SQL or AlloyDB in Mumbai or Delhi.
Target Database Choices and Their Thresholds
Managed service or database on VM
Prefer managed services when no blocking features exist and the database is under the service's size limits: patching, backup and HA come included. Choose VMs when the instance uses OS-level access, unsupported features, third-party agents or ISV certification that names an OS. Expect 60-80 percent of SQL Server instances to fit SQL Managed Instance or RDS without change.
When to flag an engine change
Flag Oracle or SQL Server Enterprise instances as engine-change candidates when automated conversion covers 85 percent or more of code objects and the application is owned in-house. Below that, or for ISV applications, keep the engine. Engine change is decided and executed later; the assessment only identifies candidates with evidence.
Oracle licensing in cloud
Oracle's policy for authorised clouds counts vCPUs rather than physical cores, typically two vCPUs per processor licence with hyper-threading. Model this against existing entitlements before choosing instance sizes; a poorly chosen instance family can double licence need. Consider license-included managed options only where support renewal is due.
Consolidation and retirement
Instances under 10 GB with fewer than 50 connections a day are consolidation candidates; databases with no connections for 60 days are retirement candidates after owner confirmation. In most estates, 10-20 percent of instances fall into these groups, directly reducing licence and migration effort.
Four-Week Database Assessment
Instance discovery and access
Instances found from discovery data and DBA records; read-only logins created.
Assessment scans and performance capture
Provider tools run and two weeks of performance and log-rate data collected.
Licence review
Entitlements reconciled with procurement and compared with target licensing.
Target selection and register
Targets, blockers and cutover estimates agreed with DBAs and application owners.
What you receive
Database Assessment Quality Measures
| KPI | Typical target |
|---|---|
| Instances with recommended target | 100 percent |
| Blockers discovered after assessment | Under 5 percent of instances |
| Instances retired or consolidated | 10-20 percent typical |
| Actual cutover duration versus estimate | Within 25 percent |
Database Assessment Pitfalls
| Risk | How NTSPL prevents it |
|---|---|
| Shadow databases missed by DBA records | Discovery process lists and ports are matched to DBA inventory to find unmanaged instances. |
| Licence position overstated | Entitlements are confirmed from contracts and support renewals, not from install counts. |
| Change rate underestimated | Log generation is measured across month-end, not a quiet week. |
Should our SQL Server databases go to a managed service or stay on VMs in cloud?
Default to a managed service, Azure SQL Managed Instance, Amazon RDS for SQL Server or Cloud SQL for SQL Server, unless the assessment finds a reason not to. Managed services remove patching, backup and HA engineering, and in our assessments 60-80 percent of SQL Server instances qualify with little or no change. Keep a database on VMs when it relies on OS access, unsupported features such as certain CLR or file-system calls, third-party agents, or an ISV that certifies only specific OS builds. For a few very large or very latency-sensitive databases, VMs give more control over storage layout. Decide per instance, not per estate.
Key facts: Data & Database Assessment
Data & Database Assessment in Practice
2 Data & Database Assessment scenarios, from Credit information and data analytics and Furniture and home-furnishing retail, plus related platform case studies.
Credit-data analytics firm assigns targets to 46 databases and halves Oracle licence need
Furniture retailer maps 23 databases across AWS and Azure and retires 4 legacy systems
NBFC moves loan-origination Oracle database to Aurora PostgreSQL and drops EE licences
Microfinance lender moves loan SQL Server to Managed Instance in an 18-minute cutover
Data & Database Assessment: Frequently Asked Questions
How long does a database assessment take?
About four weeks for up to 100 instances. Two weeks of performance capture across a month-end drive the timeline. Larger estates add analysts rather than weeks, as long as read-only access is granted promptly. Instances that cannot grant access are assessed from DBA-supplied metadata instead.
What does a database assessment cost?
Typically 12-20 consultant days depending on instance count and engine mix. Oracle licence analysis adds effort because entitlements usually need reconciling with contracts and support renewals. The register and licence model are handed over for procurement to use in renewal negotiations.
How does DPDP Act 2023 affect database migration planning?
Databases holding personal data are flagged so the target design includes encryption, access logging and an Indian-region location where required, and so test copies are masked before they move. The register records personal data per instance. CERT-In log retention needs are recorded for database audit logs as well.
Can we combine migration with an engine change?
Sometimes, but it raises risk. The assessment flags candidates with conversion coverage and ownership evidence; many organisations migrate first on the same engine, then change engine as a separate project. Engine change is safest when conversion coverage is high and the application is owned in-house.
What about databases older than supported versions?
SQL Server 2012 and 2014 instances usually need an in-place or side-by-side upgrade during migration. We estimate compatibility-level changes and test effort per instance. ISV applications may also need certification against the newer version, which the vendor must confirm in writing.
Does the assessment include file-based data like Access or FoxPro?
Yes. File-based databases behind business processes are inventoried with their owners, and each gets a target, often conversion to a managed database or retirement. Finance teams are often surprised how many month-end processes depend on these files.