Microsoft SQL Server installation

You need to install and run the required version of Microsoft SQL Server before installing the Historian.

Configure the following Microsoft SQL Server options before installing the Historian. If you already have Microsoft SQL Server installed, you can run the Microsoft SQL Server setup program to change these options. Microsoft SQL Server options should only be configured by a qualified Windows or SQL Server administrator. For more information, see your Microsoft SQL Server documentation.

• Microsoft Client Utilities must be installed.

• The Historian must run with the Microsoft SQL Server default instance name (that is, the computer name).

• During the Database Engine Configuration step of the SQL Server installation, make sure to add the Network Account and/or the local Administrators group as authorized users.

• Remote Microsoft SQL Servers are not supported by the Historian.

• For networking support, use named pipes and any other support required at your site. However, you must select at least named pipes and TCP/IP sockets (the defaults). It is highly recommended that you do not modify the default configuration for named pipes and TCP/IP sockets.

• As you select the path to the data files, you must consider that the Historian Runtime database will grow, especially if you are going to use the event subsystem (including summaries) or storing data in the ManualAnalog, ManualDiscrete, or ManualString tables.

• The Microsoft SQL Server services should be installed using the local system account. The account you specify should be an account that does not change often, if ever.

• For obvious security reasons, you should not use a blank password for Microsoft SQL Server.

• Both case-sensitive and case-insensitive SQL Servers are supported. However, you should avoid mixing case-sensitive collations in tiered Historian topologies.

• The SQL Server e-mail functionality requires a Windows domain user account. You can change the service account after SQL Server is installed. However, it is highly recommended that you use an account for which the password does not change often. For more information on SQL Server e-mail, see your Microsoft SQL Server documentation.