Emergency
ERP down, disk full, database offline. We take technical charge immediately, protecting the data first.
ERP DATABASE · EMERGENCY AND PREVENTION
ERP down, slow or with the database at risk? We take it from here.
We recover the database, get the ERP back online and put backup, monitoring and performance in order, so it doesn't happen again.
Database healthsample data
- Longest freeze
29 min→ 3 min - Maximum data loss
24 h→ 30 min - Backup per night
360 GB→ 92 GB - Blocking waits
22%→ 3% - Deadlocks per day
10→ 0
Does any of this look familiar?
- Server disk 98% full
- ERP won't open: database down
- Database log bigger than the database itself
- Work order screen slow to open
- Users stuck waiting for someone else to finish
- Slowdowns always at the same time
- Invoicing stuck at month-end close
- Invoice lookup taking almost 1 minute
- Backup running into business hours
- Backup failed and nobody noticed
- Database maintenance still running at 9 a.m.
- Slowdown came back after an ERP update
- Last restore test: never
When we get called
Protection
Backups never tested, log out of control, no integrity checks.
Performance
Slow screens, stuck users, routines weighing on the database.
CASE · EMERGENCY RESPONSE
The ERP went down in the middle of implementation.
A packaging manufacturer was in the middle of its ERP implementation when the database log file grew until it filled the server's entire disk. The system stopped, and more than 6 months of implementation work were at risk. A previous attempt to shrink the log had not fixed the root cause.
What we did
- We took technical charge of the crisis.
- We paused the ERP so the log would stop growing.
- We freed up disk space and handled the log while preserving the data.
- We validated the database and put the ERP back into operation.
- We implemented full backups twice a day, periodic log backups and daily monitoring with alerts.
- We planned and executed the database migration to a new disk structure.
- Day 1
Containment: ERP paused, space freed up, log handled.
- Day 2
Database stabilized, no data loss. Backup and monitoring in place.
- Day 3
New disk structure planned.
- Day 7
Migration window and strategy defined.
- Day 11
Database migrated, monitoring active.
0data lost
+6 monthsof implementation preserved
11 daysfrom crisis to new structure
4 routinesof protection in place
Real case at a packaging manufacturer. The recommendations were documented: dedicated storage for data, log and backup, periodic restore testing and continuous disk monitoring.
I'm in a similar situationBefore and after.
- Longest freeze
29 min3 min- Maximum data loss
24 h30 min- Backup written per night
360 GB92 GB- Deadlocks on the most critical table
30
Real case at a printing company, with 19.5 GB less in the database. In another tuned routine, reads per execution dropped 99.6%.
What we analyze.
Protection
Backup, retention and restore testing
Database integrity
Jobs with failure alerts
Disk, log and tempdb
Stability
Blocking and deadlocks
Memory and server configuration
Application server
Impact of ERP updates
Speed
Indexes and heaviest queries
Statistics and maintenance
Routines and integrations weighing on the database
Database and attachment growth
What keeps running afterward.
- Full and log backups, with retention
- Scheduled integrity checks
- Log and disk monitoring
- Email alert when something fails
- Indexes checked after every ERP update
Rules that never change.
Data comes first: a backup is identified before any action.
Read-only until the diagnosis.
Nothing is changed in the ERP vendor's objects.
Everything from SENSO IT stays outside the ERP database.
Every fix comes with a script, a rollback plan and an approved window.
Evidence before opinion: every finding comes with proof.
HOW IT WORKS
From symptom to cause, with proof.
01
Alignment and access
02
Baseline (1 day)
03
Monitoring (7 to 15 days)
04
Evidence-based diagnosis
05
Measured fixes
06
Follow-up
FREQUENTLY ASKED QUESTIONS
Frequently asked questions.
KEEP EXPLORING
Keep exploring.
BOOK A CALL
Shall we talk about your operation?
Tell us the challenge. We reply within 1 business day to schedule the best time.