I've inherited a SQL Server 2005 database 9.00.4035.00 SP3 Standard Edition that has a stored procedure call a Matlab assembly. We applied SP3 to this server. 32 Bit 8 GB RAM (2.33 GHZ x 8CPU)
and now we are getting unloads due to memory pressure.. I assume that SP3 is more rigorous in regards to UNSAFE items.
The unload Message in SQL Server error logs
AppDomain 2 (BEST.dbo[runtime].1) is marked for unload due to memory pressure.
We get this type of scenario.
A. Matlab takes space creating memory pressure.
B. REDGATE SQLBackup6 Log Backups fail (due also to CLR memory issues?)
C. Matlab gets unloaded
D. We cannot recreate the assembly as there is not enough space left.
E. We need to restart the SQL Server service to have enough space to rebuld the assembly. The Buffer pool is full
I'm a bit wary to set a -g startup parameter to the sqlservr.exe since we are in a clustering environment without a real way to test it thoroughly first. i.e my failover cluster server for SQL server is a DEV/QA sql server instance until the
failover occurs. (I did not architect this by the way).
So does anyone have any suggestions in regard to getting MatLab to function again under SP3? It ran fine albeit likely obtrusively and rough under SP2. No-one was watching for unloads for unexplained s
View Complete Post