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: Friday, November 21, 2014 9:08 AM
Points: 1,194, Visits: 2,228
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, October 29, 2014 3:39 PM
Points: 4, Visits: 57
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: Tuesday, November 25, 2014 9:53 AM
Points: 62, Visits: 460
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
Posted Friday, August 29, 2014 8:54 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, August 29, 2014 8:59 AM
Points: 1, Visits: 43
The issue with Websense is caused by a memory leak on the ODBC driver running on the Websense Logserver machine that makes connection to the SQL server. You should run the following query to identify if the leak is actually caused by the Logserver component

select * from sys.sysprocesses

Check the memusage column in this output. Any values higher than 10 indicates a memory leak situation. You can check out if any entries in the memusage column are higher than 10 and then check the Program Name column. If it says "Websense Log Server" then the leak is caused by the SQL Native client

The Websense Logserver component uses SQL Server Native client to connect to your instance of SQL server

When a prepared statement such as sp_prepare is executed, the SQLFreeStmt ODBC API function does not release the handles of the prepared statements

In this scenario, a memory leak may occur in the instance of SQL Server.

Please see the following microsoft KB

http://support.microsoft.com/kb/2422010

In order to fix this issue please upgrade your version of SQL Server Native Client (ODBC Driver) that is running on the Logserver machine. Upgrading the Native Client version to R2 SP2 (CU5) should fix the issue. You can check the current patch level of your Native client at the registry key below

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion

Please follow the above microsoft KB for applying necessary fix.

This is an issue caused by the SQL native client, therefore any applications using SQL Server Native client to make a connection to the SQL server will have this issue. Hence the issue is not Websense specific.


Ravi Desai

Technical Lead
Websense UK Ltd

MCTS - SQL Server 2008
Post #1608650
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse