I have SB setup as a fire and forget setup. I have identified that SB is the cause of my TEMPDB growing out of control. It allocates many pages but never deallocates any. The initiator ends the conversation straight away, while the target ends with cleanup, I have no conversations hanging around in the sys.conversations_endpoints table but I never see the conversation move to the CD status they always remain in the DI DISCONNECTED_INBOUND status.
Question 1 is this the cause of TEMPDB filling up.
Question 2 should the allocated pages in TEMPDB clear out when with cleanup is executed.
I know both are bad but that is the way it is setup.