I recently created a SQL database that has to store files as blobs but before doing so a vb.net CLR function performs an MD5 has on the file to store with it.  Everything runs great typically except for on occassion a very large file (4MB) will come along and blow the following error, “.NET Framework execution was aborted by escalation policy because of out of memory“.

To date I’ve tried several settings on SQL Server (2005) unsuccessfully so for now the only way I’ve been able to get around this is to run this SQL command:

DBCC FREESYSTEMCACHE ('ALL')

Running the above SQL command allowed memory to be cleared so the file could be loaded.

Previous research has shown possible fixes based around MemToLeave setting of SQL Server which appears to be a major undertaking!