I have an interface in CLR between SQL Server and the Exchange Web Services to Sync and send emails between applications. In testing this it works(ed) without any problems; we are seeing sporadic issues in the production environment where longer web service task appear to be have overlapped.
My question is very simple and I cant decide from reading the CLR details on MSDN – is CLR Thread Safe or not out of the box.
If not what is the best way of making calls to CLR that are thread safe is to applocking around my procedures or is there a less drastic alternative.
Thanks for your responses; we are coming around to this being an EWS / Impersonation issue rather than a SQL Issue. We have done a new set of load tests out of hours on the system and even under massive load (1000x higher than the application has seen so far) we can’t see a memory leak / threading issue which is why we are now looking elsewhere..
Having done much independant testing on CLR now (deliberately trying to make it fail) if your CLR code is written properly -nicely declare variables with initialisation values it appears that the CLR is thread safe.