Common questions about database health checks
What does a database health check include?
A Fortified Data database health check covers six areas: environment discovery, performance, security, availability, cost, and scalability. Each area produces severity-rated findings, a root cause for each finding, and a specific remediation step, collected into one report with an overall health score.
How is a database health check different from database monitoring?
Monitoring reports what is happening now and alerts when a threshold is crossed. A database health check examines configuration, architecture, security controls, licensing, and growth trend together, and finds the problems monitoring is not configured to see. A backup job that reports success every night but has never been restore-tested is the clearest case: monitoring records it as healthy, and only an assessment that tests the restore establishes whether it is.
Which database platforms can Fortified Data assess?
Microsoft SQL Server, Azure SQL, Oracle, PostgreSQL, and MySQL, running on premises or in AWS, Microsoft Azure, and Google Cloud. Fortified Data assesses a mixed estate in a single engagement and reports it in a single document, rather than splitting it across separate platform reviews.
What do you receive at the end of a database health check?
A comprehensive assessment report containing an executive summary with the overall health score, a technical analysis with severity-rated findings and root cause analysis, measured performance baselines, growth projections, and a remediation roadmap split into immediate actions, short-term initiatives, and long-term strategy, each with resource requirements and projected return.
Does a Fortified Data health check cover scalability and growth planning?
Yes. Fortified Data consolidated its separate scalability assessment into the health check, so one engagement covers performance baselines, historical growth analysis, workload distribution and read and write separation, partitioning and caching strategy, auto-scaling and resource allocation, and a storage and performance forecast.
How does a database health check help with a cloud migration?
A migration scoped without a baseline carries existing performance and licensing problems into a place that is more expensive to run them. A Fortified Data health check establishes the performance baseline, identifies the workloads that should be redesigned rather than lifted, and reports cloud readiness and cost impact, so the migration business case rests on measured numbers.
Do you need to be a managed services client to request a health check?
No. The Fortified Data database health check is a fixed-scope engagement that stands on its own. Organizations use it to decide whether to remediate internally, to scope a project, or to size a managed service, and the report is written so that any of those routes is possible.
How much does a database health check cost?
Fortified Data scopes each health check to the number of database instances, the platforms involved, and whether the environment runs on premises, in cloud, or both, so there is no single list price. Scope and price are agreed before the assessment begins.