SQL DBA Maintenance Epicor-specific Best Practices?


I’ve had to put on many new hats recently, one of which is becoming the point person for all things SQL. I can write basic to medium level T-SQL and somewhat know my way around SQL Server Management Studio, but I am not a DBA – very little experience with Maintenance plans, backups, indexes, growth settings, etc…

We have some managed services folks that we may be able to outsource a lot of this to. My question to you all is: what, if any, are the Epicor-specific best practices, requirements, or recommendations that a DBA should know? Basically, if we outsource DBA tasks to a seasoned SQL Server expert who knows nothing about Epicor, what do they need to know about Epicor?

Don’t edit the database directly…

Here’s a link to the Epicor KB with the basics.

It is authored by the esteemed @aidacra

Hope that helps.

1 Like

Thank you, this is helpful. I’m not seeing much in terms of Epicor-specific items; seems like standard SQL Server recommendations, which is good.

clean up the logs every month at least, epicor performance tool would give you a list of the settings you should change on your DB to maximize performance, a managed services firm will not do any of this, customers we have worked with that have a managed services group working on their servers usually end up having more problems than solutions. Your Epicor APP server and DB server are not like any other server, Epicor has specific settings that need to be care for.

We have had customers go down beacuse their managed services team decides to reindex the DB. or have a process doing back ups every night, so MRP would take hours to run, so ve very careful with whom you give this privileges.

A daily data back up is recommended, clean up on the logs, an a month reindexing done properly will optimize your DB quite a bit.

Clean up your app server logs as well, those take a gigantic amount of space.

@Hally - that link doesn’t list anything specific to the user accounts (both domain (Active Directory) and E10). Particularly what access needs to be allowed, and what should be restricted.

1 Like

Point well taken @ckrusen.

Did anyone already say DON"T EDIT DATA DIRECTLY! haha. You can use the Epicor REST API’s if you need to update data externally.
Take ownership of the database and don’t let anyone touch it that is not familiar with how Epicor works. If you are new to SQL take the time to learn what you need to get by and the rest will come over time. Keep your support contract up to date with Epicor. While they are not perfect, still provide pretty good support that will get you out of a jam a lot quicker most of the time than trying to get someone unfamiliar with the system tinkering around (they could end up voiding your support contract as well).
Good Luck.