Microsoft.SqlServer.Management.XEvent.Linq.dll missing from SMO redistributable msi - by Jonathan Kehayias

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


14
2
Sign in
to vote
ID 746688 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 6/5/2012 9:07:00 AM
Access Restriction Public

Description

The Microsoft.SqlServer.Management.XEvent.Linq.dll library is not included in the SMO download for the SQL Server 2012 Feature Pack, which makes it a non-distributeable DLL and basically restricts the streaming provider for XEvents to systems that already have SSMS installed on them.  The Microsoft.SqlServer.Management.XEvent.dll and Microsoft.SqlServer.Management.XEventEnum.dll files are in the SMO redistributable msi for the Feature Pack but to deploy a tool that uses the streaming provider for Extended Events in SQL Server 2012, you have to have the Microsoft.SqlServer.Management.XEvent.Linq.dll library as well.
Sign in to post a comment.
Posted by jchampagne on 6/7/2013 at 7:18 AM
I realize this is "resolved" now, but do we have any guidance (either from MS - or if Jonathan has heard anything) on when to expect a SMO redist refresh to actually happen? The current package in the 2012 Feature Pack is very old - dated 3/6/12. I have a new product that I'd love to release shortly that would use this DLL - or I need to consider rolling my own XEL parsing? As a side note, this DLL requires 32-bitness - can this be changed to Any CPU? (I see some native calls using Reflector, but are they *really* necessary?) Thanks in advance,
- Joel
Posted by Microsoft on 5/24/2013 at 3:52 PM
Hello Jonathan. Thanks for bringing this to our attention. This problem has been fixed. The correction will be included in a future release or servicing release for SQL Server. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by Microsoft on 8/14/2012 at 9:12 AM
Thanks Jonathan,

We're looking at options for correcting this oversight.

Regards,
Mike Wachal
SQL Server