Last week we had an issue where we could not get a PO to print for a supplier. Turns out it was for a new ship to that is in Canada. When I looked at System Monitor the error referenced a STRING_SPLIT error.
Contacted Epicor and googled it and got a recommendation to up our compatibility level on the SQL Server 2017 to the 140 level from the 120 level I had it set on. Great PO and Subcontract Pack Slip now printed.
However, there were some SSRS custom reports that started taking 3-5 minutes to render where they had been seconds. Not all reports, just some. And when those were running the SQL Server CPU pegged out at 100%. Not good. I contacted Epicor again, since they assured me that upping that level would not affect anything else in our system.
I put compatibility back at 120 since the Intern’l supplier POs will be few and far between so I’ll just work around it. But now there is a dashboard that shows a “Bad SQL Statement - See Logs” error. When I review the logs, it shows that same STRING_SPLIT error. Not sure why all of a sudden I am seeing these issues since we moved to our current 2022.2.14 back in April.
Now Epicor is suggesting that I do and setup Index Maintenance on the SQL Server but no recommendations on frequency.
Any thoughts or additional information on how we can move forward would be greatly appreciated. I am no SQL expert, and it is such an integral part of the system, I am trying to find a solution to get everything my users need without crashing our system. 😀
Thanks
Melissa
Best answer by melissah
View original