August 9, 2021 at 4:01 pm
I'm a little late to this reply, but with respect to my comment about service broker - if you set it up, I'd check to make sure you are following best practices with it and that it is working how you expect. For example, starting a conversation is a slow process, so you should reuse conversations. That being said, long running conversations can be problematic as well. My approach (based on testing of my system) is to end all open conversations on Friday during company downtime and start new ones immediately after ending the open ones.
But another thing to check would be your service broker queues - are they excessively large? Are messages being delayed in delivery due to the volume? Are there errors in service broker?
Mind you, the min, max and average wait times for your broker waitfor events are not large so they would not be the best bang for your buck.
But I think this goes back to the age old question - what problem are you trying to solve? As Jeff (and others) have said - waits are a symptom of the problem. If your finger hurts so you chop off your hand, you fixed the symptom (your finger no longer hurts) but didn't fix the problem and actually only made things worse.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply