SQL Server Manager: Microsoft SQL Server on Linux and Windows

SQL Server Manager handles DBA work on Linux and Windows, from databases stuck offline and blocked sessions to backups and index maintenance, within limits you set.

REQUEST DEMO

READ THE DOCS

2501's SQL Server Manager specialty handles SQL Server DBA work on Linux and Windows: databases that will not come online, blocked sessions, storage running low, backups and index maintenance. Nothing destructive runs without a verified backup, and it acts only as far as you allow.

A database is stuck offline, a data or log file has filled its drive, or one session is holding up a queue of others. The fix is often routine, but on a production instance a careless one is expensive: delete the wrong log backup and a restore that worked yesterday no longer does.

What 2501 does

The SQL Server specialty takes these requests from your ticketing system, whether a server runs one instance or several. It investigates databases that are offline or stuck, a service that is down, failed connections, blocking, and memory or disk pressure. It carries out routine DBA work: taking and verifying backups, index maintenance, integrity checks and clearing old backup files. It confirms the instance is healthy after every change and records each fix with the evidence behind it.

Scope map of 2501's SQL Server Manager: it takes and verifies full backups, keeps log backups and log files until the restore chain is confirmed intact and clears old backup files, investigates databases stuck offline, blocked sessions, failed connections and memory or disk pressure, runs index maintenance and integrity checks, and repairs only after a full backup; it never drops databases or schemas and never reboots the server.

You stay in control

You choose the level, per specialty: investigate only, act after a person confirms, or act on its own within your rules.
Your restore chain is protected: log backups and log files are not deleted until the backup chain is confirmed intact, and a repair runs only after a full backup.
Access is the hard limit: the agent holds only the access you grant, and destructive commands can be blacklisted outright.
On-prem, cloud or hybrid: 2501 runs wherever you do. On-prem, no data leaves your network.

Frequently asked

Does it work with SQL Server on Linux? Yes, as well as on Windows, where 2501 reaches the server through Windows remote management.

Will it drop a database or reboot the server to fix a problem? No. Dropping databases and schemas, and rebooting the server, are outside what the specialty may do.

Problems it handles

Each page is one kind of ticket, and how this specialty handles it within the limits you set.

A drive filled by a SQL Server transaction log and old backup files gets space back after 2501 confirms the backup chain is intact, and the instance is checked healthy after every change

Problem

SQL Server transaction log full

Deleting old log backups frees a SQL Server drive and can break the backup chain a restore needs. How 2501 frees space only once that chain is confirmed intact.

See how it is handled

SQL Server Manager: Microsoft SQL Server on Linux and Windows

What 2501 does

You stay in control

Frequently asked

Related

Problems it handles

SEE IT ON YOUR OWN INFRASTRUCTURE