Rockwell Automation FactoryTalk Historian SE 4.0 Installation and Configuration Guide - Manual (Page 29)

Installing FactoryTalk Historian Chapter 3
Rockwell Automation Publication HSE-IN025A-EN-E–September 2013 29
Module Database (MDB). Over time, Rockwell Automation will
transform MDB applications into AF applications. To provide
backward compatibility, FactoryTalk Historian SE 4.0 copies the
contents of Historian MDB over to AF, in a process called
transition. After the migration, the Historian server constantly
synchronizes the MDB content with AF, allowing you to access
MDB content from AF clients as well as MDB clients. Similarly, you
can access AF content from MDB clients, as well as AF clients. This
allows you to access your AF content with MDB-based tools, such as
ACE, or with an AF client such as FactoryTalk Historian System
Explorer.
AF itself requires Microsoft SQL Server. See "Install Microsoft SQL
Server (page 21)" for more information.
NOTE
Before installing FactoryTalk Historian Asset Framework, learn about the
installation options it offers. See "Installation Modes for FactoryTalk
Historian Asset Framework (page 29)" for more information.
The default installation installs the AF service and Microsoft SQL
Express on the computer with the Historian SE server installed. If
you are using a Historian server collective or will be creating large
numbers of AF elements, install both the AF service and the SQL
server on a computer separate from the Historian server. For more
information, refer to the section on FactoryTalk Historian Asset
Framework system requirements in the
FactoryTalk Historian SE
Release Notes.
During the installation process, you can decide how the AF service
and the AF SQL database will be installed on your computer, by
choosing one of five installation modes representing the following
scenarios:
• Both the service and the database are located on the same
machine:
Installation Modes for
FactoryTalk Historian Asset
Framework