Microsoft Dynamics SL
Microsoft Dynamics SL SQL Maintenance Plan
There are a handful of critical maintenance steps that must be in place in your Dynamics SL deployment to ensure the performance of the application and the security of your SQL data. These include setting up a backup plan for SL, setting up SL correctly, setting up SQL to optimize performance, and configuring SL and SQL to be adequately backed up with your business continuity/disaster recovery solution.
The worst-case scenario is that when you need to restore a backup, it does not work, and you lose days, weeks, or months of data. We encourage all SL clients to schedule a database backup and tuning checkup today. We are charging a flat rate of $195 per SQL server for this service.
Every SQL installation and network backup is different so that no one-size-fits-all procedure will work. We set up a discovery call with the finance person responsible for Dynamics SL and with your IT support. Our service ensures we can coordinate our efforts, maximize your confidence in your backup, and optimize SL for best performance. We set up a remote session with proper security to check and apply our proven setups for SQL and Dynamics SL.
Performance tuning is a new offering we have developed with the skills of our newest team member, John Koflowitch. John has strong SQL knowledge and ensures SQL is configured to backup properly, compliment your other backup processes, take up the minimum amount of space, and, in many cases, significantly increase performance. We often see improvements in lookups, processing, and report processing time. The most important result will be confidence that your SL data is restorable if the worst happens.
- Verify backup solutions are in place and functional
- Database integrity checks
- Rebuild indexes
- Run clean up tasks
- Scheduled to run weekly or more frequently as required
Why Is This Important?
- It helps prevent performance issues from occurring, bogging down the ERP system, and impacting employee productivity.
- Our checkup ensures database integrity. If you are backing up a corrupt database, it’s not going to be able to be restored if you need it.
Some Common Pitfalls We Have Seen
- Databases set to shrink nightly. The shrinking process should not be used unless the database is being decommissioned.
- Databases set to autogrow in 25 MB increments. There are many ways to configure autogrowth, but 10% is typically best.
- Many clients have nothing set up as far as maintenance plans. They need plans to check database integrity, rebuild indexes, cleanup history, etc. The maintenance plan should determine how backups are implemented and set up database backups if necessary.
- Full database backups being done by both SQL and another solution. Competing backups break the backup chain rendering transaction log backups useless until another full backup occurs by performing transaction log backups. This step is critical if you need to restore to a point in time other than the full backup.
What We Check/Verify/Create
- Backup methods (SQL or another solution like Datto, VEEAM, Intronis, etc.)
- Create a maintenance plan to include database integrity checks, rebuilding indexes, and clean up tasks to be run once a week or more frequently if needed.
Request a call to discuss this valuable service today or call Michael Milligan at 614-568-2119
Disclaimer: AccuNet cannot warrant that our service will ensure a successful backup, we are following best practices that increase the chance of a successful backup, but we are just one step in a data recovery plan.