Placement of sys.conversation_endpoints and sys.transmission_queue

Is there any thought going into moving these two tables to a file group that we can control? Putting this in Primary with the rest of my system tables is quite problematic, and hinders my ability to manage space usage on my files. Traditionally, we didn't have to consider a primary file group that could grow to large proportions, but now with these two tables it can. If a large volume of messages gets sent through and the system can't keep up, then these tables and my primary file group will grow sometimes enormously.

There are no plans to support this in the near future.

Rushi

|||

Ouch! This will be real painful, as whenever messages queue up it chews up a large amount of space. I would think that we are not too disimilar from other high transaction systems, and really don't want our primary file groups to fill up with anything other than schema definition and not require a large amount of space. This may be something important to consider, as it requires us, your customers, to plan in a completely different way than we have had to previously.

Thanks!

|||

You can submit this feedback here:

http://connect.microsoft.com/SQLServer

Rushi

|||

I agree and have raised a suggestion on connect.

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=249443

|||

The connect item has been closed

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=249443

but no comment on why it has been closed.

|||Operator error, the issue should be still active.|||Thought as much, any view on a resolution?