After uninstalling VS2011 Developer Preview SQL Server2008 R2 establishing a database relationship "Unable to find the specified module" Error resolution _MSSQL

Pity my C-disk was only 8.XG, so I had to unload it.

Unloading itself is not a problem, just last night suddenly found that SQL Server 2008 R2 Management Studio suddenly could not create a new database diagram, the establishment will report "The specified module (MS Visual Database Tools)" Error:

I even carefully evaluated the possibility of reconfiguring the database for this error. Helpless this R2 SQL2008 dozen SP1, whether it is to repair or reload are very time-consuming things, so unwilling to find a lap on Google. Finally found a similar topic to reflect this problem. An international friend reported that the title is "SQL Server 2008 R2-" Specified Module cannot be Found. (MS Visual Database Tools) ", in fact, is the same error (his English version ...) ）。 Unfortunately, this topic said that the same people encountered the problem, although a lot, but they did not find a solution.

According to their experience, the following method has been confirmed to be invalid:

Reload SQL2008 (I want to include a fix)
Re-install the. NET Framework 3.5
Reload VS2010 and VS2010 SP1
They didn't discuss what was going on. If you say they have progress, it is one of the buddies who chose the "reload system" to it ...

As a Win7 has not been installed after the formal release of the system, this solution is indeed a bit ... Not acceptable.


2. Settle it yourself.
The great leader, Chairman Mao, said, "Do it yourself."

The process of finding the reason is slightly ... In fact, using Process Monitor to observe the load operation when creating the diagram, to see which is the failure, to say it is balabala a bunch of chronological, not to mention. The reason for the final finding is: "No Msvcr11.dll found."

A discerning eye will know that this is the accompanying VC runtime in VS2011, but why the SQL Server 2008r2 still needs it after uninstalling the VS2011, the problem may only be explained by Microsoft. (perhaps VS2011 updated the shared components used by SQL2008 R2?) ）

Now that you know the reason, it's easy. Find the "Packages\vcruntimeminimum_x86\vcruntimeminimum_x86.msi" installation in the VS2011 Developer Preview installation package. A 64-bit system might put "Packages\vcruntimeminimum_amd64\vcruntimeminimum_amd64.msi" in a better position. So, in retrospect, when I unloaded the VS2011, I took the attached components for granted and didn't need them, so I deleted them together. It appears that deletion has the risk of deletion need to be cautious ah, some things are really not you want to delete, want to delete can be deleted. Hey.