How to Install SQL Server 2012 CLR Types and Report Viewer on SQL Server 2008 Without Upgrading

While deploying an ASP.NET application that uses Report Viewer 2012 to a SQL Server 2008 environment, you might encounter dependency issues with SQL CLR types. The key question is whether these components can coexist without requiring a full SQL Server 2012 installation.

The Microsoft Report Viewer 2012 Runtime requires two core components:

Microsoft SQL Server 2012 CLR Types
Microsoft SQL Server 2012 System CLR Types

These can be installed independently from SQL Server 2012 through the Microsoft SQL Server 2012 Feature Pack.

Here's the complete process to get Report Viewer 2012 working with SQL Server 2008:

Download the SQL Server 2012 Feature Pack from Microsoft's official site
Run the following installers (in this exact order):
```
SQLSysClrTypes.msi
ReportViewer.msi
```
Verify installation in Programs and Features

After installation, test the configuration with this simple ASP.NET page:

<%@ Page Language="C#" %>
<%@ Register Assembly="Microsoft.ReportViewer.WebForms, Version=11.0.0.0" 
    Namespace="Microsoft.Reporting.WebForms" TagPrefix="rsweb" %>

<html>
<body>
    <form id="form1" runat="server">
        <rsweb:ReportViewer ID="ReportViewer1" runat="server">
        </rsweb:ReportViewer>
    </form>
</body>
</html>

Common issues to watch for:

Version conflicts (ensure all references point to Version=11.0.0.0)
Missing DLL registrations in GAC
IIS application pool running under wrong .NET framework version

While this setup works, be aware of these limitations:

Some 2012-specific features won't be available when connecting to SQL 2008
Future upgrades might require compatibility testing
Performance characteristics may differ from native 2012 environments

If you encounter persistent issues, consider:

Using SQL Server 2008 R2 (which has better compatibility)
Implementing a report server middle tier
Converting reports to a different format

When deploying an ASP.NET application that utilizes Report Viewer 2012 on a SQL Server 2008 instance, you might encounter the missing "CLR Types for SQL Server 2012" error. This is a common scenario when modern reporting components need to interact with older database servers.

Report Viewer 2012 requires the SQL Server System CLR types package (SQLSysClrTypes.msi) as a prerequisite. These components provide the SQL Server data types in the .NET Framework Common Language Runtime (CLR).


// Sample connection string that might trigger the issue
string connectionString = @"Data Source=SQL2008SERVER;
                          Initial Catalog=ReportingDB;
                          Integrated Security=True";

You can install just the required components without installing the full SQL Server 2012:

Download Microsoft® System CLR Types for SQL Server® 2012 from Microsoft Download Center
Download Microsoft® Report Viewer 2012 Runtime
Install both packages on your application server

After installation, verify the components are properly registered:


// PowerShell command to check installed programs
Get-WmiObject -Class Win32_Product | 
Where-Object {$_.Name -like "*SQL Server*CLR*"} | 
Select-Object Name,Version

If you encounter version conflicts with existing SQL Server components:

Check the GAC for multiple versions of Microsoft.SqlServer.Types.dll
Ensure your web.config has proper binding redirects:


<runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
      <assemblyIdentity name="Microsoft.SqlServer.Types" 
                        publicKeyToken="89845dcd8080cc91" 
                        culture="neutral" />
      <bindingRedirect oldVersion="10.0.0.0-11.0.0.0" 
                      newVersion="11.0.0.0" />
    </dependentAssembly>
  </assemblyBinding>
</runtime>

For mission-critical systems, consider:

Setting up a separate reporting server with SQL Server 2012
Using linked servers to connect to your SQL 2008 data
Implementing a service-oriented architecture with a reporting middle tier