MS SQL server msdb.sysxmitqueue table bloat
- Dominant language
- C++
- Stars
- 406
- Forks
- 134
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 24
Description
The msdb.sysxmitqueue table ends up with millions of records. Our dba has put together some questions to try to track down this issue.
1. What is the Service Broker used for in the application? What is the flow and purpose of the messages
2. Is it required in our implementation?
3. If not, Can it be disabled or removed?
4. The msdb.sysxmitqueue system table in msdb database had over 30m queue entries and bloated the DB to 35GB. Has this issue been reported before?
5. If so, what was the root cause and how is it normally fixed?
6. If not, what could potentially cause this issue - we have no message queue entries currently to help in debugging as the queue was so large it was unresponsive and needed to be reset.
7. Does the issue happen only on some versions of SQL Server - 2017 Enterprise, 2017 Express etc?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.