Managed service plans
We run your environment, with 24/7 monitoring, maintenance, and proactive improvement.
90.48% off the procedures clinicians were waiting on
Slow stored procedures on a clinical communications platform are not a database complaint. They are a delay between a medical professional and time-sensitive patient information, and they were being found by end users rather than by monitoring.
Critical stored procedures
90.48%
Faster, which removed the delays in clinical communications that users had been reporting.
- Complaints on monitored processes
- Zero
- Holiday cover delivered on
- Under 24h notice
- Platforms managed
- SQL Server and PostgreSQL
In short
What happened
A mission-critical healthcare communications platform connects medical professionals with time-sensitive patient information across hundreds of facilities, on both SQL Server and PostgreSQL. Its support model was reactive: issues surfaced when end users complained. Fortified Data improved critical stored procedure performance by 90.48 percent, set up monitoring for slow procedures and custom alerting for failed SSRS restores, and moved the arrangement from reactive to proactive, reaching zero complaints on monitored processes. It also completed a PostgreSQL logical replication project ahead of schedule with documentation and training behind it, and advised halting a high-risk AWS migration before it ran.
90.48%
Improvement in critical stored procedure performance, which removed the delays users were reporting in clinical communications.
Fortified Data case study, 2025
Zero
Complaints on monitored processes after the support model moved from reactive to proactive.
Fortified Data case study, 2025
24h
Notice, or less, on the holiday support that covered the period internal teams were unavailable.
Fortified Data case study, 2025
Why reactive support is the wrong shape here
This platform carries time-sensitive patient information between medical professionals across hundreds of healthcare facilities, so system reliability is not an operational preference. Its support model caught issues only after end-user complaints, which on a clinical communications platform means after a delay has already reached a clinician. Performance bottlenecks in critical stored procedures were affecting both the user experience and the clinical workflows behind it.
There was a capability gap alongside the coverage gap. The platform runs PostgreSQL as well as SQL Server, and limited PostgreSQL expertise was preventing the adoption of the replication strategies the platform needed to scale.
Two more pressures were arriving at once: new compliance requirements demanding rapid deployment of licensing management, and holiday periods when internal teams were unavailable and nothing covered the gap.
What the managed service did
Three workstreams, running alongside each other
Performance work, a platform expansion and an advisory that stopped a migration. None of them is a stage of the others, which is why they are three cards and not a numbered sequence.
Performance optimization and monitoring
Critical stored procedure performance improved by 90.48 percent, which removed the delays in clinical communications. Custom alerting was implemented for failed SSRS restores, which caught a critical Christmas Eve error, and monitoring for slow procedures now resolves them before users notice. The support model moved from reactive to proactive and reached zero complaints on monitored processes.
PostgreSQL expansion and growth
A PostgreSQL logical replication project was completed ahead of schedule, accelerating client onboarding before year-end, with documentation and training behind it so the deployment is repeatable rather than a one-off. It expanded the managed footprint beyond SQL Server onto a second platform.
Strategic advisory and risk prevention
A high-risk AWS migration was identified and halting the deployment advised, preventing revenue-impacting outages. The client was guided to engage Microsoft for root cause analysis rather than an unproven fix, a licensing solution was deployed with documentation to meet a new compliance requirement, and holiday support was provided on under 24 hours' notice.
What changed
- 90.48% faster critical proceduresWhich eliminated the complaints and improved the clinical communications those procedures were holding up.
- A cloud migration failure preventedThe AWS migration was identified as high risk and halted on advice, avoiding the revenue loss and system downtime that running it would have carried.
- PostgreSQL logical replication in productionDelivered ahead of schedule, with documentation and training that make the next deployment repeatable, and with client onboarding accelerated before year-end.
- Monitoring that found a Christmas Eve errorCustom alerting on failed SSRS restores caught a critical error at the point in the year when nobody was looking, which is the argument for alerting over attention.
- Compliance licensing deployed quicklyA licensing management solution with documentation, deployed against a new compliance requirement on the timescale the requirement set.
Three ways to work with us
On-Call DBA
A guaranteed 15-minute emergency response plus monthly on-demand hours that bank when unused.
Database consulting and projects
Project-based engagements for migrations, performance tuning, data modernization, business intelligence, and high availability and disaster recovery.
Are you finding problems when your users do?
The measurable part of moving from reactive to proactive is the complaint count on monitored processes. The unmeasurable part is the migration that was stopped before it ran, which never appears in anybody's figures and was worth more than the tuning.
Let us show you what's possible.