Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

User Connection Memory - Memory Leak?? Expand / Collapse
Author
Message
Posted Monday, February 24, 2014 12:48 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 4:23 PM
Points: 1,194, Visits: 2,209
Try using this option "Optimize for Adhoc workloads " .. This reduces memory consumption by adhoc query plans and helps in eliminating procedure cache excessive consumption.

On 32 bit systems, Procedure cache is limited in size. 64 bit systems are OK.

--
Best Regards
Post #1544686
Posted Monday, February 24, 2014 4:20 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, July 2, 2014 2:22 PM
Points: 4, Visits: 50
To cut the connection you can loop the connections by the account and kill them or set single mode for the wslogdb70 database and set back multi mode.

Alter database wslogdb70 set SINGLE_USER with rollback immediate
Post #1544736
Posted Tuesday, March 18, 2014 1:18 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Today @ 2:13 PM
Points: 62, Visits: 405
Hi,

You need to change the websense setting from ODBC to BCP.Its a known bug in ODBC drivers which keep the connection open from websense log.
Post #1552371
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse