A few months ago we were hit by some ransomware and had to re-image everything, including our servers. Luckily we were able to restore from a backup we had that wasn’t too old.
Since then we’ve noticed Epicor has been running poorly. Forms take forever to open, but queries seem to run fine. I’ve ran the performance and diagnostic tool on my workstation, the app server and the SQL server. I’ve fixed many of the issues that were in the configuration but some still have me concerned and I have a few questions.
#1 - CPU, having some conflicting results with PDT and the CPUtest provided by @hkeric.wci in another article. My question is, is this testing the local machines CPU or one of the servers CPUs? Also, why would PDT give me a vastly different result than the CPUtest exe?
#5, our DB was 166GB, which seemed rather large, PDT said to reduce the size. So I ran a shrink on it, which knocked it down to 88GB, but PDT is still complaining it’s too big. Any tip, tricks or suggestions here?
#6, any ideas on how we can increase SQL Query performance?
Since you were a victim of ransomeware, I think it is safe to assume that some changes have been implemented in the IT infrastructure of the company. Any chance that those security measures might be set a little too strict with regards to the E10 system and clients?
#1 Not sure #2 check the Server Tracing under Application Server Setting (on the App Server). #3 could be the Patch level of SQL 2017… Just s thought #4 why would you NOT? #5 That is a very large Log file. If you are getting that large of a file, you may need to perform backups more regularly. It will shrink the file automatically. If you aren’t using SQL for backups/disaster recovery, you can look into other options like Simple Recovery.
@ckrusen, other than doing a company wide password reset and forcing some mandatory cyber security courses, not much has changed… Except for the new vacancy in the IT department lmao.
@Jason_Woods, the flags were disabled before I started investigating. I enabled them globally last Friday but noticed they were disabled again this morning… Too many hands in the pot. You’re correct, 14.00.23 is the patch level of SQL 2017, but to get to where we need to be it looks like we need to upgrade to 2019, my question is would this improve performance? I believe we have Veeam setup to take nightly backups but I will investigate this further.
