Close SQL Complete connection to SQL Server when not being used.
When running sp_who2 I can see tasks for "dbForge SQL Complete" for each user running SSMS even when it's not doing anything. (I guess the connection is pooled between each request that the application needs to make?)
Anyway, our admins don't like to see all of these jobs just hanging around doing nothing, especially on our live servers. Any chance of turning off your connection pooling?
1
vote
Duncan Hine
shared this idea
We would like to let you know that we have released dbForge SQL Complete, v5.6 where the issue you reported is fixed https://www.devart.com/dbforge/sql/sqlcomplete/download.html
Thank you for your help in improving dbForge SQL Complete.