SQL Server care for NAV & on-premises Business Central
Planned Microsoft SQL Server maintenance and focused incident support for the database layer behind Dynamics NAV and on-premises Business Central.
Choose the right path
A planned review reduces avoidable risk. An incident engagement stays tightly focused on the operation that must be restored.
Planned maintenance
Urgent support
Business Central Online uses a Microsoft-managed database layer. For application, workflow, integration or cloud service incidents, use LeXurey’s broader ERP recovery service.
View ERP recoveryClear skill set
The work does not stop at making SQL look healthy. The affected NAV or on-premises Business Central workflow also needs to be understood, restored and checked.
Instance, database, file, job and maintenance-plan review for production ERP environments.
Evidence-led analysis of waits, blocking, deadlocks, long-running work and resource pressure.
Review recovery objectives, backup chains and restore readiness before making recovery-sensitive changes.
Right-size growth settings, review storage headroom, and target the bottleneck affecting the operation.
Connect database symptoms to service tiers, sessions, jobs, integrations and the business workflow users rely on.
Record the incident, confirm the affected workflow, and leave practical follow-up actions for the internal team or ERP partner.
Anonymised support anecdote
A user reported that Dynamics NAV had stopped operating normally. Investigation moved below the application and identified excessive SQL Server transaction-log growth and depleted usable capacity.
The practical lesson
Shrinking a transaction log may be one controlled recovery step after log reuse is addressed; shrinking alone is not the maintenance strategy.
Recovery sequence
Check the database, storage, backups and recovery constraints before changing production.
Use a controlled transaction-log procedure that preserves the agreed recovery path.
Confirm the application and affected workflow, then document backup, capacity and monitoring follow-up.
How support works
Confirm what stopped, when it changed, who is affected and which recovery constraints matter.
Check database state, backups and available capacity before production remediation begins.
Address the immediate cause, then validate the database, NAV or on-premises Business Central service, and the affected workflow.
Document the finding and agree monitoring, backup, capacity or maintenance follow-up separately.
Share the symptom, the time it started, affected users or workflows, NAV or on-premises Business Central version, SQL Server version, exact error text, recent changes and known backup status.
Do not send passwords, connection strings, database files or customer data through the public form or website chat. A secure transfer path can be agreed separately.
Describe the affected operation. LeXurey can help separate planned database care from the incident work needed now.
