Installing SQL Server 2012

You typically install Microsoft® SQL Server 2012 and Content Manager OnDemand on the same system. The database that is used by the Content Manager OnDemand instance is created locally and is on the local file system.

Although it is not preferred, it is possible to run the Content Manager OnDemand server against a remote SQL Server database. In this case, the database is on a different server than the one on which the Microsoft SQL Server is installed.

Microsoft SQL Server 2012 requires Microsoft .NET Framework 3.5.1 to be installed. On Windows 2008 R2 server, this step is not completed by the Microsoft SQL Server 2012 installation process. Complete this step by using the Windows 2008 R2, 2012 or 2012 R2 Server Manager outside the Microsoft SQL Server 2012 installation.

In the Server Manager interface, select Features on the left pane and select .NET Framework 3.5.1 from the list.
Click Add Features on the right pane if .NET Framework 3.5.1 is not shown.
Follow the screen directions to install the feature and restart, as instructed.

This limitation also applies to Microsoft SQL Server 2014, but does not apply to Microsoft SQL Server 2008 R2.

To install Microsoft SQL Server on the library server:

Click setup.exe to start the SQL Server Installation Center.
Select Installation on the left pane.
Select New SQL Server standalone installation or add features to an existing installation.
Make sure that there are no failures on the Setup Support Rules panes.
On the Setup Role pane, select SQL Server Feature Installation.
On the Feature Selection screen, select Database Engine Services, Client Tools Connectivity, Documentation Components, and Management Tools - Basic.
Make sure that there are no failures on the Installation Rules pane.
On the instance Configuration pane, select Default instance.
On the Database Engine Configuration pane, select Mixed Mode (SQL Server authentication and Windows authentication) and specify a password for the Microsoft SQL Server admin ID, sa.
The Mixed Mode authentication is needed to create a new SQL Server user ID later to be used by the OnDemand instance owner.
Click Add Current User to also add the logged on Windows user ID to the Microsoft SQL Server and click Next.
Make sure that there are no failures on the Installation Configuration Rules pane.
When the Microsoft SQL Server 2012 installation completes, make sure that there are no errors, close the SQL Server Installation Center, and restart the server, if needed.
Start the Microsoft SQL Server 2012 Management Studio and connect to Database Engine.
Click Security and expand Logins on the left pane.
The Windows user ID used to install Microsoft SQL Server 2012 is listed but in the form of <domainname>\user_name. Create a SQL Server login without the host name or domain name.
Right-click Logins and select New Login...
Enter the name of an existing Windows user ID with administrator rights, such as odadmin.
This name is the user ID that is used to create the OnDemand instance.
Select SQL Server Authentication and enter a password for the new Microsoft SQL Server user ID.
Accept the default database name master.
On the Server Roles page, make sure that the dbcreator box is checked.
Click OK to create the new login.

Before you can create the Content Manager OnDemand Instance with Microsoft SQL Server 2012, you must verify that a correct version of the regasm.exe file exists. Content Manager OnDemand is released with an SMO (SQL Server Management Objects) DLL that needs to be registered by regasm at installation time. Content Manager OnDemand V9.0 uses a 64-bit v2.0.50727 RegAsm.exe file. Content Manager OnDemand V9.5 and V10.1 use a 64-bit v4.0.30319 RegAsm.exe file.

A v2.0.50727 RegAsm.exe file is normally available on the Windows Server 2008 R2 while a v4.0.30319 RegAsm.exe file is normally available on the Windows Server 2012 and Windows Server 2012 R2.

On systems without a v2.0.50727 RegAsm.exe file, you can install .NET Framework 3.5. This solution includes 2.0 and 3.0. If .NET Framework 3.5 is not installed, SQL 2008 R2 can install it automatically. Microsoft SQL Server 2012 and 2014, however, does not install .NET Framework 3.5 automatically. On Windows Server 2008 R2 and higher, you might need to use Server Manager to install it from the feature selection pane.

On systems without a v4.0.30319 RegAsm.exe file, you can install .NET Framework 4 or 4.5. If .NET Framework 4 is not installed, run the Windows Update to install it. To find out which version of the regasm.exe file is installed, run following commands from a Windows command prompt:

C:\>CD C:\Windows\Microsoft.NET

C:\Windows\Microsoft.NET>DIR regasm.exe /s/b

The sample output shows that both versions are installed.

C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\RegAsm.exe
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe

If Content Manager OnDemand V10.1 is installed without a 64-bit v4.0.30319 RegAsm.exe file, the Content Manager OnDemand SMO DLL cannot be registered. Any attempt to run arsdb to create an SQL Server database might result in a system crash. Make sure that you have a 64-bit v4.0.30319 RegAsm.exe file before you install Content Manager OnDemand V10.1.

If Content Manager OnDemand V10.1 is installed without a 64-bit v4.0.30319 RegAsm.exe file, install .NET Framework 4.5.1 manually or by using the Windows Update.
After you verify that you have a 64-bit v4.0.30319 RegAsm.exe file, reinstall Content Manager OnDemand V10.1.
Alternatively, you can apply the most recent Content Manager OnDemand V10.1 fix pack, such as 10.1.0.1, to register Content Manager OnDemand SMO during the installation.

To verify whether Content Manager OnDemand SMO is successfully registered, look for the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{ECC6E2B2-9901-4A26-
AEF0-085507A375EF}\v.r

where v.r can be 9.0, 9.5, or 10.1 for Content Manager OnDemand V9.0, V9.5, or V10.1, for example.

Microsoft SQL Server 2008 R2 can install .NET 3.5 automatically but does not install .NET Framework 4 automatically. For Content Manager OnDemand V10.1, .NET Framework 4 is required but not installed automatically by Microsoft SQL Server 2008 R2. For this reason, install Microsoft SQL Server 2012 for Content Manager OnDemand V10.1.