SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


User Connection Memory - Memory Leak??


User Connection Memory - Memory Leak??

Author
Message
sqlbuddy123
sqlbuddy123
SSCertifiable
SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)

Group: General Forum Members
Points: 6530 Visits: 2243
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
kfqwang
kfqwang
SSC Rookie
SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)

Group: General Forum Members
Points: 46 Visits: 89
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
deepakgupta86
deepakgupta86
SSC-Enthusiastic
SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)

Group: General Forum Members
Points: 102 Visits: 734
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.
Ravi Desai
Ravi Desai
Grasshopper
Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)

Group: General Forum Members
Points: 19 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
sqlnewbieDBA
sqlnewbieDBA
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 343
Did you mean "2008R2SP2CU5" or "2008R2SP1CU5". Because apparently this issue was resolved in SP1CU5. Currently our server is on SP1CU9 and we are seeing user connection memory rising slowly over time. Please advice as I have been looking into this for a while and don't know what to do regarding it. Based on some of the posts I have seen some people say it was fixed after installing SP2 while some say it did not get fixed. We are currently on websense version 7.7
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search