Service · Remote DBA and database monitoring

Remote DBA and database monitoring for SQL Server, Oracle, MySQL and PostgreSQL

IDS monitors your databases, handles the alerts, and does the ongoing DBA work that keeps them healthy. You get experienced coverage across SQL Server, Oracle, MySQL and PostgreSQL, on premises or in the cloud, on a monthly retainer, with one point of contact and a clear monthly report, and without hiring a full-time DBA for each engine.

Good fit when

  • You have production databases but no dedicated DBA, or one DBA covering too much.
  • You run more than one engine and can’t hire a specialist for each.
  • Backups “succeed” but nobody has tested a restore lately.
  • Performance problems keep coming back and get fixed by restarting the server.
  • An upgrade or end-of-support deadline is coming and nobody owns it.
  • Your DBA is leaving, retiring or overloaded, and you need continuity.

What we monitor

We use our own monitoring tools or the ones you already have, depending on your environment. Checks run on a schedule against each instance we support. What we watch:

  • Health and availability
    • Instance and service status, uptime and restarts
    • Connection counts and failed logins
    • Error logs and alert logs
    • Replication, log shipping, cluster and standby status where you use them
    • Database consistency checks and corruption warnings
  • Performance
    • Long-running and expensive queries
    • Blocking, deadlocks and lock waits
    • Wait statistics and resource pressure (CPU, memory, I/O)
    • Baselines and trends, so “slow” is measured against normal, not a guess
    • Plan changes and regressions after deployments or upgrades
  • Backups and recovery
    • Every scheduled backup checked for success, size and timing
    • Backup chains and retention checked against your recovery goals
    • Restore tests on a schedule agreed with you, with results in the monthly report
    • Point-in-time recovery readiness where the engine supports it
  • Jobs and maintenance
    • Scheduled jobs and agents: failures, long runs and missed runs
    • Index and statistics maintenance, or VACUUM and ANALYZE on PostgreSQL
    • ETL and SSIS job outcomes where they touch the databases we support
  • Capacity
    • Disk, data file, log and tablespace growth
    • Temp space and transaction log usage
    • Growth trends with a forecast of when you’ll run short
  • Security and patching
    • Logins, roles and elevated permissions reviewed for changes
    • Default, shared and orphaned accounts flagged
    • Patch and version levels tracked against vendor releases and end-of-support dates
    • Configuration drift from your agreed baseline

How alerts are handled

Monitoring is only useful if someone acts on it. Here’s how an alert moves:

  1. Detected. A check fails or a threshold is crossed. Thresholds are set with you during onboarding, so the alerts that reach people are the ones that matter.
  2. Reviewed. An IDS DBA reviews it during the coverage hours agreed with you and decides whether it’s urgent, routine or noise.
  3. Fixed or escalated. Routine issues, like a failed job, a full log or a stuck backup, are fixed within the agreed scope. Anything that needs a change window, an outage or a business decision goes to your point of contact first.
  4. Communicated. You’re told what happened and what we did, through the channel agreed during onboarding.
  5. Recorded. Every alert and action goes into the monthly report, and repeat alerts get a root-cause fix, not just another restart.

Coverage hours, agreed with you

Alert review hours are set per client, not fixed by tier. Options include business hours, extended hours or around-the-clock coverage, and we agree what fits your systems and your budget before monitoring starts.

Getting started

We start with a review of each instance, agree thresholds, coverage hours and escalation contacts, and connect in the way your security team prefers. Then we document what “normal” looks like for your environment.

What the monthly report includes

Each month you get a plain-English report you can forward to management:

  • SummaryOverall health of each instance and anything that needs a decision.
  • Alerts and incidentsWhat fired, what we did and how it was resolved.
  • Backups and restore testsBackup success, and the result of any restore test that month.
  • PerformanceTop resource-heavy queries, the trend against last month, and tuning work done.
  • CapacityCurrent growth and a forecast of when storage limits will be reached.
  • Security and patchingPatch levels, permission changes and accounts flagged.
  • Work completedChanges, maintenance and requests handled, with time used against the retainer.
  • RecommendationsWhat we’d fix next, ranked by risk.

Hands-on DBA work

Beyond monitoring, the retainer covers day-to-day and planned DBA work:

  • Performance tuning: queries, indexes, configuration and server settings
  • Patching and version upgrades, planned around your change windows
  • Backup and recovery design, and restore runbooks
  • High-availability and disaster-recovery setup and support
  • Migrations between versions, servers or engines, and to or from Azure and AWS
  • User, role and permission management
  • Overflow hours when your own DBA is out or overloaded

Recent database work

Anonymous examples from ongoing engagements.

UTF-8 migration of a federal reference database

We moved a production SQL Server database for a federal science agency to UTF-8. We analyzed byte capacity, widened only the columns that needed it, scripted the migration so every run was repeatable, and checked row counts, referential integrity and generated output on each pass.

Legacy SSIS export replaced

For the same agency, we replaced a legacy SSIS export package with standard SQL and PowerShell, and verified that the regenerated output matched the original.

SQL Server performance tuning

On a shared production database, one key stored procedure went from 70.5 seconds to 3.6 seconds, about 95% faster, with identical results verified.

Engines and platforms we support

  • Microsoft SQL Server and Azure SQLOn-premises SQL Server, Azure SQL Database and Azure SQL Managed Instance. Availability groups, failover clusters, log shipping, SQL Agent jobs, SSIS, query tuning, and upgrades off out-of-support versions.
  • Oracle Database, including RACRMAN backup and recovery, Data Guard standby, Real Application Clusters, tablespace and storage management, performance tuning, patching and upgrades.
  • MySQL and MariaDBReplication, backups and point-in-time recovery, InnoDB tuning, slow-query analysis and version upgrades.
  • PostgreSQLStreaming replication and failover, backup and point-in-time recovery, VACUUM and bloat management, query tuning, extensions and major-version upgrades.
  • Amazon RDS and AuroraManaged SQL Server, Oracle, MySQL, MariaDB and PostgreSQL in AWS: parameter tuning, snapshots and restore tests, performance analysis, and version upgrades.

Retainer options

The same service at three levels of scope. Every tier is month-to-month and scoped to your instances and engines. Each tier includes everything in the tier before it. Alert coverage hours are agreed per client and aren’t tied to a tier.

ScopeCare LiteCore (most common)Plus
Best forSmall estate that mainly needs watchingMost mid-market environmentsLarger, multi-engine or business-critical estates
Onboarding review and baselineIncludedIncludedIncluded
Monitoring: health, performance, backups, jobs, capacity, securityIncludedIncludedIncluded
Alert review and notification, in agreed coverage hoursIncludedIncludedIncluded
Monthly health reportIncludedIncludedIncluded
Routine alert fixes (failed jobs, full logs, stuck backups)Within the included DBA timeIncludedIncluded
Restore testsAvailable on requestOn an agreed scheduleOn an agreed schedule
Scheduled maintenance (indexes, statistics, VACUUM, consistency checks)Checked and reportedRun and tuned by IDSRun and tuned by IDS
PatchingTracked and recommendedApplied in agreed windowsApplied in agreed windows
Performance tuningTop issues flaggedOngoing tuningOngoing and in-depth tuning
CapacityReportedReported, with recommendationsPlanned with you for growth and platform changes
Security and permission reviewsChanges flaggedReviewed and cleaned upReviewed, cleaned up and hardened to a baseline
High availability and DRStatus monitoredMonitored and maintainedAdministered and planned with you
Upgrades and migrationsPlanned and advisedAdvised, with smaller upgrades handledUpgrade and migration work scoped into the retainer
Hands-on DBA timeSmall monthly blockLarger monthly blockLargest monthly block
PricingContact us for a quoteContact us for a quoteContact us for a quote

Development and Microsoft data work can be added to any tier.

Questions we hear

Do we have to replace our current monitoring tool?
No. We use our own tools or the ones you already have, depending on your environment.
Do you monitor around the clock?
Coverage hours are agreed with each client. Business hours, extended hours and around-the-clock coverage are all options.
Can you cover just one engine?
Yes. Retainers are scoped to what you run, from one instance to a mixed estate.
Do you support cloud databases?
Yes, including Azure SQL Database and Managed Instance, and Amazon RDS and Aurora.
How do you connect to our systems?
In the way your security team prefers, agreed during onboarding.
Is there a long contract?
No. Retainers are month-to-month.

Tell us which engines you run, roughly how many instances, and what’s keeping you up at night.

Get a quote →