AppDomain 2 (mssqlsystemresource.dbo[ddl].1) unloaded in SQL Server Log

Periodically we see the following messages in one of our SQL Servers:

AppDomain 7 (mssqlsystemresource.dbo[ddl].6) unloaded.

Unsafe assembly 'microsoft.sqlserver.mpusqlclrwrapper, version=10.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 4 (mssqlsystemresource.dbo[runtime].3).

AppDomain 4 (mssqlsystemresource.dbo[runtime].3) created.
AppDomain 3 (mssqlsystemresource.dbo[ddl].2) unloaded.
AppDomain 2 (mssqlsystemresource.dbo[ddl].1) unloaded.

Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\Windows\Microsoft.NET\Framework64\v2.0.50727\


Is this anything to be concernened about?

Thank you
aiopsitAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Ryan McCauleyConnect With a Mentor Data and Analytics ManagerCommented:
I wouldn't be concerned as long as you're not seeing any connection drops or other negative behavior associated with the message.

SQL Server (starting with 2005) allows .NET code to be called from T-SQL (with proper configuration and precautions). The term "UNSAFE" (in the .NET assembly sense) isn't a term to be concerned about - it just denotes an assembly that may access components of the system that are protected. Specifically (from TechNet):

UNSAFE  code permission is for those situations in which an assembly is not verifiably safe or requires additional access to restricted resources, such as the Microsoft Win32 API.

Though I've never seen this message specifically, it just means that SQL Server has unloaded the assembly to free up memory or because it's not currently being used.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.