Brighthouse Financial · Insurance · Dynamo
Batch queries cut from nearly 30 minutes to seconds
Brighthouse Financial is a US life insurance and annuity provider managing more than $240 billion in assets.
~30 min to secondsCritical query runtime
| Area | Before | After |
|---|---|---|
| Batch runs | Recurring SSIS failures | Fixed at the root |
| Know-how | Known by a few people | Batch flows documented |
The problem
- Industry
- Insurance
- Our role
- Production support and development
- Location
- North Carolina, United States
Brighthouse ran about 100 daily batch jobs on tables nearing 500 million rows. As volumes and upstream files grew, runs became unstable and SSIS failures recurred.
Date-based queries on very large tables could take nearly 30 minutes because of missing indexes. Business users uploaded reports without timely data, which reduced trust.
We joined midstream, while jobs still ran every day. Frequent manual fixes stretched the internal team and put SLAs at risk.
The system’s scope had grown with little documentation, which made troubleshooting slower and riskier.
What we built
Stabilizing daily operations came first. We triaged every live batch incident, found root causes and coordinated fixes with upstream and downstream owners.
We redesigned fragile process paths so failures stayed fixed. One fix swapped memory-heavy SSIS handling of multi-gigabyte files for lightweight line-ending detection.
We identified missing indexes on high-volume tables, optimized query paths, and documented batch flows and dependencies with diagrams.
The result
- Daily batch jobs stabilized
- About 100
- Rows in the largest tables
- Nearly 500 million
- Relationship
- Renewed
Critical queries that took nearly 30 minutes now run in seconds. The repeated batch failures were fixed at the root.
With fewer incidents and faster recovery, the internal team spends less time on manual fixes.
Onboarding and troubleshooting no longer depend on what a few people remember. Teams trust the data again.
