Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.databases.ms-sqlserver > #1972 > unrolled thread

unsafe assembly message in the sql server log

Started by"M.G." <michael@gurfinkel.us>
First post2016-09-09 14:42 -0700
Last post2016-09-10 11:37 +0200
Articles 2 — 2 participants

Back to article view | Back to comp.databases.ms-sqlserver


Contents

  unsafe assembly message in the sql server log "M.G." <michael@gurfinkel.us> - 2016-09-09 14:42 -0700
    Re: unsafe assembly message in the sql server log Erland Sommarskog <esquel@sommarskog.se> - 2016-09-10 11:37 +0200

#1972 — unsafe assembly message in the sql server log

From"M.G." <michael@gurfinkel.us>
Date2016-09-09 14:42 -0700
Subjectunsafe assembly message in the sql server log
Message-ID<3657fc10-eb2d-481e-b115-12d2074200d0@googlegroups.com>
We started getting messages like this one:

2016-09-08 08:00:54.18 spid91  Unsafe assembly 'microsoft.sqlserver.mpusqlclrwrapper, version=10.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 215 (mssqlsystemresource.dbo[runtime].285).

in the server log (MS SQL 2008 R2)

I don't know much about assemblies and the message worries me.

My understanding is that assembly usually is a procedure written in CLR language, such as C#, compiled and deployed as native code on SQL Server.

There is no s/w that we build and deploy as such assembly - what could be a reason for the warning message? Are there any steps to further investigate it?

[toc] | [next] | [standalone]


#1973

FromErland Sommarskog <esquel@sommarskog.se>
Date2016-09-10 11:37 +0200
Message-ID<XnsA67F763848A16Yazorman@127.0.0.1>
In reply to#1972
M.G. (michael@gurfinkel.us) writes:
> We started getting messages like this one:
> 
> 2016-09-08 08:00:54.18 spid91  Unsafe assembly
> 'microsoft.sqlserver.mpusqlclrwrapper, version=10.0.0.0,
> culture=neutral, publickeytoken=89845dcd8080cc91,
> processorarchitecture=msil' loaded into appdomain 215
> (mssqlsystemresource.dbo[runtime].285). 
> 
> in the server log (MS SQL 2008 R2)
> 
> I don't know much about assemblies and the message worries me.
> 
> My understanding is that assembly usually is a procedure written in CLR
> language, such as C#, compiled and deployed as native code on SQL
> Server. 
> 
> There is no s/w that we build and deploy as such assembly - what could
> be a reason for the warning message? Are there any steps to further
> investigate it? 
 
Note that this assembly comes from the mssqlsystemresource database, that 
is the system database that inlcudes all system procedures, catalog views
etc.

I don't know about the mpusqlclrwrapper, and the documentation I find on
https://msdn.microsoft.com/en-us/library/microsoft.sqlserver.management.shared.mpusql.mpusqlclrwrapper.aspx
isn't that detailed. However MPU = Multi-Processor Unit or some such.
This is related to what now is known as the Parallel Data Warehouse and
which first appeared in the SQL 2008 R2 timeframe. Since that is a 
specialised version of SQL Server, it is not appearent why it would be
loaded on a plain-vanilla instance.



-- 
Erland Sommarskog, Stockholm, esquel@sommarskog.se

[toc] | [prev] | [standalone]


Back to top | Article view | comp.databases.ms-sqlserver


csiph-web