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
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.
Websense UK Ltd
MCTS - SQL Server 2008