IIRC, for TN DB I don’t think we can control which connection is used for which types of operations. For 6.x we get to define a single pool only for TN use.
One of the things that may help considerably is creating index on heavily used columns of specific tables. For 4.6 we had created these indexes:
NativeID on BizDoc
DocTimestamp on BizDoc
UserStatus on BizDoc
StringValue on BizDocAttribute
ServerID on DeliveryJob
TimeCreated on DeliveryJob
TimeUpdated on DeliveryJob
JobStatus on DeliveryJob
These were the columns we typically used in TN Console when looking at activity. The DocTimestamp index on BizDoc in particular had a huge impact on TN Console performance.
I haven’t looked at the indexes provided out of the box for 6.x TN (there might be additional indexes provided than what was there for 4.6) but there may be similar benefits gained from adding indexes on the columns you use heavily for queries.