April 4, 2013 at 10:49 am
Hi There,
I hope this is in the right board, the SQL CLR section seems to be under SQL Server 2005.
I have a CLR Assembly that contains methods to encrypt and decrypt a table of fields using AES.
We see a large performance hit on the first run of these methods whilst the CLR is loaded into memory. This takes between 15 and 20 seconds. Subsequent calls take < 1 second until the Assembly is unloaded.
I have done some reading around AppDomains and it seems that the AppDomain is held in memory 'to improve performance' until such time as SQL Server deems that 'memory pressure' requires it to be unloaded.
We will be hitting these methods quite often but not consistently enough to prevent the CLR from unloading.
Is there anyway to adjust the server settings or assembly options to make them more persistent?
TIA,
Chris
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy