Hope your testing’s gone well and things go smooth for you.
We’ll see what the weekend brings us.

Hope your testing’s gone well and things go smooth for you.
We’ll see what the weekend brings us.

Good luck everyone!


And this doesn’t bode well for the weekend. We just went down live…
Us too. Just came here looking for others.
I have a ticket in.
We are down as well. Wasn’t going to start a new thread as I was waiting for someone else! Our pilot is working just not Live. ![]()
Yeah it’s the usual cut-and-paste formletter notification that they send every time there’s an outage.
![]()
OK, Which one of you ran the recursive query on PartTran…
Another outage caused by their SQL server. Eek. Doesn’t inspire confidence they fixed their SQL problems.
Ah, sounds like a repeat of our CS0005200259
2025-11-14 14:39:40 -NAME REDACTED-
We noticed a recent memory spike in the system. The DBA team has informed us that a new implementation will be applied to prevent this issue from recurring. Please note that this change is scheduled for this weekend.
So that was five months ago and here we are.
EDIT: Sorry @Randy but I took away the solution…“you will succeed” must have been a jinx or a hex. ![]()
BAQ:
We are back up ![]()
We limit that internally for this reason, I guess not everyone subscribes to this process.
And it’s running about as slow as it was at 1155a ET…five minutes before it dropped.
EDIT - another update:
We have identified the cause of the incident and are implementing a solution.
We are closely monitoring the situation to ensure the issue is fully resolved.
Confidence level?
Ours is very quick!
I received internal notification about 20 minutes ago that this incident which affected a fairly small (but important) set of our customers is over.
If you continue to have any issues, please report them to Support.
Having a shared architecture that could let one persons errant query break a cluster of ERP systems is poor structural design not an issue with people having access to SQL