SQL Server Home
Microsoft SQL Server 2008 R2 Shared Management Objects (x64) are missing 32-bit version of Microsoft.SqlServer.BatchParser
as Won't Fix
10/26/2010 5:10:17 AM
User(s) can reproduce this bug
When I am installing Microsoft® SQL Server® 2008 R2 Shared Management Objects from the Feature Pack release (6/7/2010) the 32-bit assebly Microsoft.SqlServer.BatchParser is not installed, only a 64-bit version of the assembly is installed. To verify this i looked in the folder C:\Windows\Assembly. In this folder i only find the assembly with Process "AMD64", not a x86 version.
I have noticed the same problem with the Feature Pack for SQL Server 2008.
If I install SQL Server 2008 R2 Express (x64) both the 32-bit and 64-bit version of the assembly is installed. Also if I install SMO from SQL Server 2005 Feature Pack both 32-bit and 64-bit versions of the assembly is installed.
The only workaround I have found so far is to install both 32-bit and 64-bit version of SMO on the computer but this does not seam right.
SQL Server 2008 R2 - Express Edition
Windows 7 Enterprise
Operating System Language
Steps to Reproduce
Install Microsoft® SQL Server® 2008 R2 Shared Management Objects from the Feature Pack release (6/7/2010) on a Windows 7 x64 OS.
Try to run a 32-bit application that needs the Microsoft.SQLServer.BatchParser.dll assembly and it will fail. If you look in the folder C:\Windows\Assembly you will see that there is only a "amd64" version of the Microsoft.SqlServer.BatcherParser.dll assembly.
I exepted to find 2 Microsoft.SqlServer.BatchParser.dll assembly of version 10 in the folder C:\Windows\Assembly, one that is x86 and one that is amd64. This is the result I get if I install the Microsoft SQL Serverf 2008 R2 Express and I think the result should be the same.
to post a comment.
Please enter a comment.
on 11/7/2011 at 4:49 PM
I was hoping for a better answer as I'm having the same problem above and installing 32 and 64 bit versions of SMO has not fixed it. What a rigmarole!!
on 1/7/2011 at 10:36 AM
Removing support of 32-bit ODBC makes it so I cannot connect to my database using Crystal Reports. Given the popularity of Crystal Reports I find it abominable that my so-called "upgraded" version does not allow me to do the one thing I need to do with it. I tried to find an earlier version (MSSQL 2008) just because of this, but of course big brother MS had blocked it from the shelves, forcing me to buy R2.
You can run ad campaigns to promote how much better MS is now, but with this kind of BS going on behind the scenes people who know what they are talking about will continue to despise MS. So maybe the SQL Server Manageability team should let the MS Marketing team know what an epic fail this is.
on 11/19/2010 at 4:13 AM
Greetings from the SQL Server Manageability team.
Thanks for writing in to Microsoft. We greatly value your feedback. We understand your problem, and how fixing this could improve productivity.
However, prioritizing against our current set of deliverables, and that there is a workaround that is available (installing 32 bit smo) we do not think, we would be able to get to this in the near future.
Having said that, we value your suggestions, and would like to assure you that, we would keep these ideas in mind, when we do revisit this feature in the future.
Thanks again for providing feedback and making SQL Server the greatest Database server.
to post a workaround.
Please enter a workaround.
© 2014 Microsoft