db24.ai

A one-sentence summary

DB24 is an intelligent operations platform that can be deployed within existing Microsoft SQL Server environments in enterprises; it automates backup and routine maintenance tasks, provides centralized monitoring of database health, tracks changes in configurations and permissions, and uses an AiQ score ranging from 0 to 10 to indicate which issues require priority attention.

Tool Introduction

DB24 was developed by the Swedish company DB24 AB; it is designed to serve as a substitute for SQL Server on autopilot. It transforms the processes of monitoring, maintenance, backup, and fault detection, which previously relied on a small number of database administrators, into configurable and trackable automated tasks.

It is not an online AI assistant designed for generating SQL statements in natural language or for creating business databases, nor is it a hosted database service. The software is installed in the customer’s local environment as DB24 CORE, and it operates through a central Datastore, a Runtime component on each instance, and a Web Portal.

Product architecture

Central Datastore

The Datastore is responsible for aggregating the information collected by multiple Runtimes and storing historical data, thereby providing information on instances, databases, backups, capacity, jobs, and security status in one place. The official documentation states that the Datastore runs on SQL Server, or it can be deployed as a sidecar on existing instances.

Local Runtime

Runtime is a proxy component that is installed on each managed SQL Server instance; it consists of a small Runtime database, SQL Server Agent jobs, and stored procedures. It collects health and performance metrics locally, and carries out maintenance tasks such as backups, index creation, and statistics updates.

Web Portal

Portal serves as a unified management interface through which teams can view insights, configure automation, and manage the entire SQL Server environment. It allows IT managers, system administrators, and DBAs to use the same set of data, eliminating the need to check the logs of each individual server separately.

Main functions

Automatic discovery in SQL Server environment

Once connected, DB24 creates a centralized list of instances, databases, and configurations, which helps teams identify databases that have been forgotten, are rarely used, or lack a designated owner. The results of this list should still be cross-verified with the CMDB, business owners, and the processes for disabling databases.

AiQ Database Health Score

Aggregated Instance Quality assigns a score ranging from 0 to 10 to each instance, based on criteria such as configuration, storage, security, performance, and backup and recovery. This score is used to determine the order in which inspections should be carried out, and it also provides specific suggestions for improving the score.

• View the current scores of all instances at once to identify environments with a higher risk level first.
• Compare the current score with the historical and initial scores to observe whether the improvement is sustained.
• Drill down further by main category, subcategory, and parameters, rather than just looking at the total score.
• Compare the inspection results with Microsoft’s standards and industry practices to create a list of actions for improvement.

Automated database backup

DB24 allows for the scheduling of full backups on a per-instance basis, as well as optional differential backups and transaction log backups; it also automatically retries failed tasks. Even if an enterprise uses other backup solutions, the platform can still provide a centralized view of the status of those backups.

• It supports backup compression, and integrity verification can be performed upon completion.
• Complete, differential, and log backups can be scheduled based on the recovery mode and database size.
• Large databases can be split into multiple backup files to improve throughput.
• The cleanup rule will delete old files only when a new successful backup of the same type is created.
• Databases that are temporary or not required to be included in the DB24 backup can be excluded.
• Notifications can be triggered in cases of backup failure, expiration, abnormal size, or incorrect path.

Indexing, statistical information, and integrity maintenance

The platform integrates index reconstruction or reorganization, statistical information updates, database integrity checks, and file size monitoring into a unified maintenance engine. Each operation leaves behind records of the commands used, the start and end times, the duration of the operation, as well as any error messages, which facilitates auditing.

Real-time monitoring and early warning

DB24 continuously monitors the health of the instance, the status of backups, disk capacity, permissions, and any error messages, sending warnings to the appropriate personnel. Notifications should be configured based on severity, the instance to which they relate, and business hours, in order to avoid alert fatigue.

Change tracking and auditing

The platform uses DDL triggers to record changes in objects such as databases, schemas, and stored procedures, and to link these changes with the execution time, username, and commands used. Security views also provide information on instance logins, database users, roles, as well as the permissions that have been granted or denied.

Patching and lifecycle recommendations

Patch Advisor is used to compare the current SQL Server patches with the recommended targets, while LifeCycle Advisor shows the release dates of various versions as well as Microsoft’s support status. Before a patch is deployed, it is still necessary to test its compatibility in a testing environment and to determine appropriate rollback procedures.

Capacity and licensing optimization

DB24 aggregates information on instance size, CPU usage, memory usage, disk usage, as well as historical changes in capacity, thereby helping teams identify underused databases and over-configuration. The decision to reduce server or SQL Server licenses should be based on actual load levels, availability requirements, and contractual considerations.

Database usage insights

Database Engagement data is used to determine the latest activity levels of a database as well as trends in connection usage, and it can provide insights for making decisions regarding archiving, integration, or decommissioning. Low activity does not mean that the database has no business value; before decommissioning, it is necessary to obtain confirmation from the system owner and to have a restoreable backup available.

How does DB24 work?

1. Identify the SQL Server instances, network areas, service levels, and responsible persons that need to be under management.
2. Run the Environment Readiness Wizard to verify the server, account, network, and dependent conditions.
3. Deploy Datastore, Portal, and the Runtime required for various instances in the customer’s environment.
4. Datastore connects to Runtime on a scheduled basis to centrally retrieve configuration, health, and maintenance data.
5. View the environment list, AiQ score, backup status, and risk notifications in Portal.
6. Enable backup, indexing, statistics, integrity, and capacity maintenance for each business window.
7. Route the notification to the appropriate team and use historical data to verify the effectiveness of the corrective actions.
8. When it is necessary to integrate with a CMDB or generate reports, data is retrieved through supported read-only SQL views.

Installation and Getting Started Guide

Preparations before installation

1. Confirm that this project is intended for Microsoft SQL Server only, and list all instances to be connected.
2. Read the prerequisites, permissions, and installation documentation that correspond to the target version.
3. The Runtime Environment Preparation Wizard fixes missing components, network access issues, or account permissions.
4. Plan the firewall, name resolution, and credentials for the connection from Datastore to Runtime.
5. Specify the Datastore deployment instance, Portal certificate, backup directory, and notification recipients.
6. Complete installation, uninstallation, and restoration drills for the testing environment before making any production changes.

Deploy DB24 components

1. Download the official installer for the current unified version; do not use different release versions together.
2. First, deploy the central Datastore and Portal, and verify that the management interface is accessible.
3. Install the Runtime components on the first low-risk SQL Server instance.
4. Verify that the Datastore is able to retrieve Runtime data, and that the configurations are delivered correctly.
5. Check the status of SQL Server Agent jobs, Runtime databases, and service accounts.
6. After completing the small-scale verification, add the remaining instances in batches.
7. Save the version, installation parameters, account details, certificates, and rollback steps.

Enable automatic maintenance

1. First, examine the existing backup, indexing, integrity, and statistics tasks to avoid running them repeatedly.
2. Select full, differential, and log backup strategies based on the recovery point objective.
3. Set the backup path, compression, verification, retention period, and threshold for splitting large databases.
4. Define business maintenance windows for indexing, statistical information, and integrity checks.
5. First, enable it on the non-critical instances and observe changes in duration, lock waits, as well as CPU and storage usage.
6. Once the results are confirmed to be stable, gradually expand the scope while retaining the database-level exclusions.

Establish a closed-loop alarm system

1. Map instances and databases to specific business and technical owners.
2. Define notification levels based on backup, security, capacity, performance, and version risk.
3. Set rules for email or team delivery to prevent all events from being sent to everyone.
4. Set time limits for confirmation, escalation, handling, and review for each type of severe alert.
5. Regularly check for invalid recipients, duplicate events, and issues that have not been resolved for a long time.
6. Use the AiQ historical trends and maintenance logs to confirm whether the issue has been truly resolved.

Which users are it suitable for

• System administrator: Performs standardized SQL Server maintenance in the absence of a dedicated DBA.
• Database Administrator: Centralized management of multiple instances, reducing redundant scripts and routine inspections.
• DevOps and platform teams: Integrate database health, versioning, and capacity into a unified operational process.
• IT Manager: Use AiQ and reports to identify risks, resources, and priorities for corrective actions.
• Hosting service providers: Serve multiple clients or separate environments under unified rules.
• Public sector and regulated organizations: Retain backups, permissions, and audit evidence of changes.
• Medium to large enterprises: Managing a growing number of SQL Server assets with dispersed owners.

Typical use cases

Product advantages

• It covers monitoring, maintenance, backup, changes, and security information at the same time, thereby reducing the number of separate tools.
• Runtime executes tasks locally on managed instances, while the central Datastore aggregates historical data in a unified manner.
• AiQ transforms complex assessments into scalable health scores ranging from 0 to 10.
• It automatically maintains reservation commands, duration information, and error records, facilitating auditing and review.
• It can manage DB24’s own backups as well as monitor the status of backups created by third parties.
• Supported, versioned, read-only SQL views are provided to facilitate integration with internal systems.
• The local installation mode is suitable for organizations that require the database management components to remain within their own enterprise environment.

Usage restrictions and precautions

• The product is designed specifically for Microsoft SQL Server and is not a platform that works with multiple databases.
• It is necessary to install components such as databases, jobs, stored procedures, and Portal in the customer’s environment.
• Automated maintenance can affect production loads; it is necessary to evaluate the available time windows and resources before enabling it.
• The Datastore needs to be able to connect to various Runtimes; when it is deployed across different network segments, network settings and permissions must be configured in advance.
• All DB24 services should be on the same version; running mixed versions is not supported.
• AiQ is an auxiliary indicator for determining operational priorities; it cannot replace business impact analysis or the judgments of DBAs.
• Backup verification does not equate to actual recovery; companies still need to conduct regular recovery drills.
• The official website does not disclose information regarding the free version, the duration of the free trial period, or the price of the standard package.
• The licensing terms prohibit decompilation, modification, and copying; the product itself is not open-source software.
• When ceasing use, it is necessary to uninstall the DB24 database and SQL Agent jobs in accordance with the contract.

Price and licensing options

As of August 22, 2026, DB24 does not have a fixed price list that can be purchased directly. The official website asks companies to contact the support team to obtain quotes based on the scale of their environment, with the licensing fees determined by the number of software instances in use.

DB24 allows for a True-Up to be performed annually in order to verify the number of connected instances, and customers are also required to keep this information accurate throughout the duration of the agreement. When placing an order, the billing criteria applicable to testing, disaster recovery, cluster nodes, and temporary instances should be included in the quote.

What needs to be confirmed before quoting?

• Count the number of instances for production, testing, disaster recovery, and decommissioned candidates respectively.
• Verify whether annual licensing, implementation, training, upgrades, and support are charged separately.
• Understand how high-availability clusters, passive nodes, and short-term instances are billed.
• Specify the contract duration, renewal adjustments, payment currency, and taxes.
• Confirm the additional cost for the new instance and the schedule for the annual True-Up.
• Clarify the responsibility boundaries for uninstallation assistance, data export, and post-termination tasks.

Version and Download

The official installation page identifies DB24 2026.2.3 as the latest version during verification, while still offering several installation packages from the 2026.1 and 2025 series. New instances must be installed with a version that is identical to the existing DB24 environment.

Data, Privacy, and Security

The centralized data listed in the official technical documentation includes instance and database configurations, backup records, connection activities, jobs, login information and permissions, capacity details, error logs, maintenance records, and ratings. Before deployment, enterprises should verify which fields will be included in the Datastore, as well as who will have access to them through the Portal or integrated views.

DB24’s privacy policy applies to personal data of website visitors, contacts, and individuals in business relationships; it also states that the company may act as a processor in customer relations. The policy specifies that personal data is retained only for as long as it is necessary to achieve the intended purposes, and it is either deleted or securely anonymized after regular reviews.

• Adhere to the principle of least privilege by configuring separate service accounts for Datastore, Runtime, and Portal.
• Protect the Portal with trusted TLS certificates and restrict the network range of the administrative access points.
• Implement role isolation for views that contain login names, permissions, and command text.
• Define the retention periods required for operational data, change logs, and error logs based on business needs.
• Confirm the contractual arrangements regarding suppliers, sub-processors, cross-border data transfers, and data retention.
• Regularly check accounts, SQL Agent jobs, triggers, and configuration changes.
• Integrate platform alerts into the existing event response and auditing processes.
• Critical databases still require separate offline or immutable backup strategies.

Integration, APIs, and openness

The APIs mentioned in the DB24 documentation refer to versioned SQL views within the Datastore’s API framework, and not to public Web interfaces. These views provide structured data in a read-only manner, ensuring that the columns and their semantics remain consistent across different versions.

Process for accessing read-only views

1. Identify the fields that are truly necessary for the reports or CMDB, in order to avoid accessing all sensitive information.
2. Create a dedicated SQL login or service identity with the minimum required permissions in Datastore.
3. Only the API architecture views supported by the official sources are queried; no direct reliance is placed on internal tables.
4. When a stable contract is required, a view with a version suffix should be used.
5. It is hoped that official synonyms will be used when the latest structure is obtained as part of an upgrade, and that changes will be monitored.
6. Verify the new version of the view in the testing environment before updating it in the production setup.
7. Record the query frequency, entities that access the data, its destination, and the retention period.

GitHub, SDKs, and open-source status

As of the time of verification, the official website and official documentation did not provide any confirmed official GitHub organization, public source code repository, or development language SDK. The database projects with the same name that were found cannot be considered related to DB24 AB on this basis.

DB24 CORE is commercial software designed for local deployment; its licensing terms reserve ownership of the software and related intellectual property rights, and prohibit decompilation, modification, and copying without written permission. Therefore, this product should be classified as non-open source.

Supported platforms

Basic information

Recommendation score

The recommendation score is 4.2 out of 5. DB24 combines functions such as environment detection, automatic maintenance, backup, scoring, permission management, and change logging for SQL Server; it is suitable for enterprise operations teams that wish to reduce reliance on manual intervention while still maintaining control over their systems.

The main barriers are local deployment, the requirement to use SQL Server, the lack of transparency regarding prices, and the risk that automatic maintenance can introduce changes to the production environment. Before making a purchase, it is necessary to conduct limited-scale technical tests, recovery drills, and to have a clear understanding of how costs are calculated for the instances in question.

Frequently Asked Questions

Is DB24 an AI tool for generating SQL?

No. DB24 is primarily used to automate the monitoring, backup, maintenance, evaluation, and auditing of Microsoft SQL Server; it is not a chat tool that generates query statements using natural language.

Is DB24 free?

The official website does not disclose any information regarding a free version, a free usage quota, or a fixed trial period. Companies need to contact the authorities in order to obtain a quote based on the number of managed instances and any additional services required.

How is DB24 priced?

The licensing fee is based on the number of SQL Server instances connected to the software; it is usually paid in advance on an annual basis, with the quantity possibly being verified through an annual adjustment. The actual unit price and billing criteria are determined according to the company’s quotes and the main agreement.

Does DB24 need to be installed locally?

It is necessary. DB24 CORE is deployed locally and includes a central Datastore, a Web Portal, as well as Runtime components installed on managed SQL Server instances.

Will DB24 replace database administrators?

It can automate a large number of repetitive maintenance tasks and centralized inspections, but it cannot replace architectural design, assessments of business impacts, handling of complex failures, or approval processes for changes. Critical operations still require supervision by personnel with experience in SQL Server.

Which databases are supported by DB24?

The current official documentation and specifications focus on Microsoft SQL Server. There is no reliable evidence indicating that it can manage MySQL, PostgreSQL, Oracle, or other databases.

What does the AiQ score represent?

AiQ assigns a score ranging from 0 to 10 based on assessments of storage, security, performance, backup, and recovery, and provides recommendations for improvement. It is used to determine priorities, but it does not constitute a guarantee of availability or a certification of compliance.

Does DB24 provide APIs?

What is provided are versioned, read-only SQL view interfaces within the customer’s Datastore, which can be used for generating reports and integrating with internal systems. No public Web API or developer console has been found.

Is DB24 open source?

It is not open source. The licensing terms state that the intellectual property rights to the software belong to DB24 or its licensors, and they restrict decompilation, modification, and copying.

What happens after it is stopped being used?

Upon the termination of the license, use must be ceased and the DB24 software components, including the related databases and SQL Agent jobs, must be deleted or destroyed; it is specified that the customer’s own data should remain unchanged. The specific procedures for uninstallation and data export shall be defined in the contract.

Summary

DB24 is suitable for enterprises that manage a large number of or critical Microsoft SQL Server instances, as it enables the consolidation of asset discovery, health scoring, backup, maintenance, change management, and permission information into a trackable operations framework. Its value lies in standardizing processes and reducing reliance on individual contributors, rather than in generating business data or replacing all DBA decisions.

Before making a choice, it is essential to verify the permissions for local deployment, the impact on production loads, the actual recovery capabilities, the scope of the data, version consistency, and the pricing per instance. If an enterprise needs Web API access, support for multiple databases, or open-source code, then other options need to be considered or evaluated separately.