DB24_

Modules_
DB24_

Functional overview_
Generally
DB24 is an automation tool for SQL Server. The main advantage is to free up time for technical
internal resources, increase the quality of operation and make managed SQL Server databases
reliable and robust.

Although DB24 is primarily about Management and not Performance Tuning, all systems will be
easier to troubleshoot if they are managed in an efficient and predictable way (Microsoft Best
Practice). This also makes Performance Tuning significantly more efficient on a SQL instance
managed by DB24.

DB24 is for the most part parameter controlled. Everything from when certain jobs are to be run, to
naming of Test databases, backup paths, configuration of Index jobs, etc.

In addition to the fact that most are parameter-controlled and thus efficient and quality-assured, the
configuration tables are differently designed to support production, test and development
environments. We can thus tailor our governing values depending on the operating environment.

In addition to the fixed modules below, DB24 includes a large toolbox for fixing errors that may
occur, or tools for migrating data to new versions or consolidating databases into new operating
environments ("SQL hotels"). Customer-specific modules can easily and quickly go to Release,
thanks to the unique support functions that already exist and the module structure.

1
DB24_

Housekeeping
Housekeeping is the "deputy host" in the system and keeps track of the general situation,
which databases are available, which jobs are set up, paths and all important configuration
data.

01 Checks and logs current databases ("Inventory"), their configurations, and sets

put them in the appropriate class for backup and maintenance jobs.

02 Compiles all Agent Jobs, their description, status and complete schedule.

03 Updates paths and other parameters for AutoRefresh on selected databases (Applies

only at test and development bodies)

04 Checks and logs the sizes of all data files.

05 Checks and logs the complete configuration of the SQL instance

2
DB24_

Security
The security module handles logging and alerting of the security parameters that can
compromise configuration stability, intrusion, and authorization errors. No active action is taken
to prevent security incidents, only alarm and logging is done.

The module is not activated in the initial mode, but is recommended for use afterwards.
However, it is recommended to always have the monitoring of new logins and attempts at higher
rights up and running.

01 Monitors and alerts if new logins are created, executed command is logged, and under
which account and what time.

02 Monitors and alerts when trying to raise a login to SysAdmin role, i.e. top rating.
Executed command is logged, and under which account and for what time.

03 Monitors and alerts when trying to create a new Stored Procedure in the database, the new
code logged, and during which account and the bay time.

04 Monitors and alerts when trying to change Stored Procedure code in database, the new
code logged, and during which account and the bay time.

05 Monitors and alerts when attempting to change database properties, executed code is
logged, and under which account and for what time.

3
DB24_

Cost Control Services

DB24 reports monthly what each database has consumed of the license fee, in both percentages
and in kronor. Microsoft SQL Server is licensed per CPU Core. Each organization has a licensing
agreement with Microsoft that defines the annual cost in dollars and dimes.

All that is needed is to enter the standard cost per CPU Core in the DB24 configuration, which is
done initially and takes minimal time. Thereafter, the cost automatically falls out per database and
SQL instance monthly in a standard report. It has never been easier to debit internally, construct
Business Case for resource allocation, etc.!

In addition, DB24 can provide budget managers with a helicopter view of how much work the
various SQL instances do to each other. It will thus be possible to make a list of which SQL
instances perform the most work and which work the least.

A given area of use is to appoint candidates to merge / consolidate SQL instances and thereby
increase efficiency as well as save large sums.

A minimal saving of a couple of cores reduces IT expenses by at least 5,000 - 15,000 per year.
Intelligent choices can often save 6-10 cores in a medium-sized environment without other
measures.

4
DB24_

Operations
Operations är modulen som proaktivt bearbetar datafilerna storleksmässigt, som bevakar
tröskelvärden, håller reda på Servicefönster, och som sänder ut ev. begäran om mer disk till berört
system. Modulen håller även koll på användningen av databaser och loggar vilka som ansluter till
instansen. Allt sker 24/7.

01 Scheduling of Maintenance Mode (means shutting down surveillance during

service window)

02 Continuously monitors data files, proactively increases file sizes to eliminate AutoGrowth,
and logs changes.

03 Monitors disk filling, orders proactive expansion of disk complete with desired size, and
logs changes.

04 Monitors and logs all connections to the instance, as well as systems that call, under
which account and which time.

05 Logs which databases are never used.

06 Responsible for running AutoRefresh on test and development databases. See separate
section below.

5
DB24_

AutoRefresh
AutoRefresh is a unique module that automatically updates test and development databases with
data from the latest backup made by DB24. The module is fully integrated with DB24 Backup and
thus guarantees error-free and fresh data.

AutoRefresh is fully configurable for naming databases, customizations (rights, etc.), database
owners, and ranges. AutoRefresh can be run on schedule or run manually. All settings are made
per database and can be made just as complex and specific as you need. No other manual
handling will be added.

All test and development databases are automatically updated, without the need for manual
intervention.

Should any update not go 100% well, alarms are sent to DBA. Service Desk can also get this
information.

Data Protection
A database system rests on the integrity of the underlying files, as well as their internal health. If an
error occurs here, production stops. This is a very critical feature.

01 Checks that all data files are complete and corrects if necessary, including logging.
02 Checks fragmentation of databases and measures if necessary, including logging.
03 Checks the index chains of all databases and measures if necessary, including Statistics and
logging. This significantly affects the performance of individual databases.
04 If needed: For really large databases (tables with> 5,000,000 rows), there is a special
function that only updates the relevant Index Statistics in a smart ("tiered") way, which
reduces the need for frequent defragmentation over time. This improves performance and
does not affect the system as badly while driving.
05 Checks extremely large log files and shrinks them correctly and securely, when they
meets the thresholds.

6
DB24_

DB24 Reports
The report module publishes via a so-called Staging process ready data base, ideal to build reports
with, or to simply download in Excel and analyze. All data is denormalized,
i.e. ready to be consumed in a simple way, readable and ready to use.

All report documents are in the form of tables in the database DB24_Reports and a Reporting
Services instance can be set up for self-service if necessary. Custom report documents are easily
produced when needed.

Standard reports as of 2019-09-01:

01 SQLInstancesDashboard
02 DataChangeLog
03 AggregatedDataChange
04 DatabaseInfo
05 SQLDataPerDisk
06 DataPerDisk
07 InstanceInfo
08 NeverAccessedDatabases
09 AgentJobsAndSchedules
10 FailedBackups7Days
11 LatestBackups

Blocking Detection
The module tracks so-called "Head blocker" and all the data around it. Invaluable when you have
problems with recurring blocking situations where an SQL instance goes hot and in the worst case
stands almost still and sprays deadlocks. The information about who the culprit is is not logged by
SQL Server in the basic version, therefore the DB24 module is needed to secure this data. With the
information you can track the exact application, server and account it is running under and fix the
error. In many cases it is about e.g. a new release of an application.

The module is optional and can be easily connected if needed.

7
DB24_

Transaction Pressure
The module provides answers to the pressure to which the SQL instance is exposed from the
outside. This information is not logged by SQL Server in the basic version, therefore the DB24 mold
is needed to secure this data. With the information, you can easily see whether the system is under
pressure and how it varies over time, as everything is time stamped. It is very useful when you have
systems that spread a lot of "noise" around you and that cannot be captured in so many other ways.

Patch Control
A SQL instance typically needs to be updated regularly to work flawlessly and securely, and for the
general Life Cycle model to work.

The Patch Control module maintains a daily updated register of all SQL patches and Cumulative
Updates (CU) Microsoft releases, and presents the current patch rate for each SQL instance, which
is an indispensable decision basis for DBA and technical manager / manager during Operations
Meetings.

8
DB24_

DB24 Backup
Backup does not just mean having a backup system installed, it is a responsibility that requires that
you always know that the backups are in place and working. Backup must never stop working
simply because Restore must always be possible! Comprehensive and functional backups are thus
the single most important task for a DBA.

DB24 Backup is probably the best and most reliable backup system on the market. Basically based
on the code for how Microsoft in Redmond backs up its internal databases.

DB24 Backup is fully automated, logs and alerts and monitors that all backups really go through.

01 Carry out fully automated backup of all databases and log all relevant
information such as status, file location, speed, backup size and more. Potential faults
logged accurately via Extended Events for deep troubleshooting, alarms immediately go out
to the DBA and agreed party, e.g. Service Desk. In addition, the built-in schedule the
backup guard a bypass of each backup if it did not go through first time. Everything is
logged / alerted and can be followed up. Overtaking is done continuously until the backup
gone through. Typically when you get to work in the morning, the backup has gone
through even if there was a problem during the night, and mail has gone out about both Fail
and Success. In case of permanent fault conditions, e.g. disk crash, or broken power
switch, can DBA need to go in and fix manually.
02 Supported backup types are Full and Log. (Diff can be activated if needed)
03 The system keeps track via Housekeeping which databases are in SIMPLE respectively
FULL RECOVERY MODE and adjusts settings automatically. Housekeeping also keeps
track of which databases are OFFLINE and excludes them automatically.
04 Individual databases can easily be excluded from backup.
05 All backups are compressed, checksum-checked and can be encrypted if needed.
06 Able to store backups in Azure, and then the backups are always encrypted.

For more information, contact NN.