Wonderware® FactorySuite®

IndustrialSQL Server™ Historian Installation

Guide

Revision E
Last Revision: 7/13/05

Invensys Systems, Inc.

All rights reserved. No part of this documentation shall be reproduced, stored
in a retrieval system, or transmitted by any means, electronic, mechanical,
photocopying, recording, or otherwise, without the prior written permission of
Invensys Systems, Inc. No copyright or patent liability is assumed with respect
to the use of the information contained herein. Although every precaution has
been taken in the preparation of this documentation, the publisher and the
author assume no responsibility for errors or omissions. Neither is any liability
assumed for damages resulting from the use of the information contained
herein.
The information in this documentation is subject to change without notice and
does not represent a commitment on the part of Invensys Systems, Inc. The
software described in this documentation is furnished under a license or
nondisclosure agreement. This software may be used or copied only in
accordance with the terms of these agreements.

© 2002-2005 Invensys Systems, Inc. All Rights Reserved.

Invensys Systems, Inc.

26561 Rancho Parkway South
Lake Forest, CA 92630 U.S.A.
(949) 727-3200
http://www.wonderware.com

Trademarks
All terms mentioned in this documentation that are known to be trademarks or
service marks have been appropriately capitalized. Invensys Systems, Inc.
cannot attest to the accuracy of this information. Use of a term in this
documentation should not be regarded as affecting the validity of any
trademark or service mark.
Alarm Logger, ActiveFactory, ArchestrA, Avantis, DBDump, DBLoad, DT
Analyst, FactoryFocus, FactoryOffice, FactorySuite, FactorySuite A2, InBatch,
InControl, IndustrialRAD, IndustrialSQL Server, InTouch, InTrack,
MaintenanceSuite, MuniSuite, QI Analyst, SCADAlarm, SCADASuite,
SuiteLink, SuiteVoyager, WindowMaker, WindowViewer, Wonderware, and
Wonderware Logger are trademarks of Invensys plc, its subsidiaries and
affiliates. All other brands may be trademarks of their respective owners.
 Contents 3

Contents
Before You Begin ...............................................5
About this Guide .................................................................................... 5
IndustrialSQL Server Documentation Set.............................................. 5
Document Conventions .......................................................................... 6

CHAPTER 1: Requirements and

Recommendations ..............................................7
Server Requirements .............................................................................. 7
High Availability Support................................................................... 9
Requirements for Historian Management Tools .................................... 9
Remote IDAS Requirements................................................................ 10
Security Considerations for a Remote IDAS.....................................11
Disk Sizing and Data Storage................................................................11
General Hardware Recommendations for Storage ........................... 12
Planning for Disk Space Requirements ............................................ 12
Disk Requirements for Software Components ................................. 13
Disk Requirements for Database Files ............................................. 13
Disk Requirements for Historical Data Files.................................... 14
Performance Considerations ................................................................ 15
Server Loading ................................................................................. 16
IDAS Performance ........................................................................... 17
Storage Subsystem Performance ...................................................... 17
Networking Recommendations ............................................................ 18
Client Access........................................................................................ 19
Client Connections to the IndustrialSQL Server Historian .............. 19
Client Connection and Workload Limits .......................................... 20
Network Protocols for Clients .......................................................... 21
Licensing .............................................................................................. 21
Historian_Tagcount Feature Line ..................................................... 22
Historian_MSCluster Feature Line................................................... 22
Historian_ServerOS Feature Line .................................................... 22
Historian_RemoteIDASCount Feature Line .................................... 23
Historian_ModifyHistoryData Feature Line .................................... 24
Historian_HistoryDuration Feature Line.......................................... 24
Historian_Processors Feature Line ................................................... 24
Support for Non-English Operating Systems....................................... 25
Integration with Other Wonderware Products...................................... 25
Anti-Virus Software ............................................................................. 26

CHAPTER 2: Installation..................................27
Microsoft SQL Server Installation ....................................................... 28

IndustrialSQL Server Historian Installation Guide

4 Contents

About the IndustrialSQL Server Historian Installation.........................28

IndustrialSQL Server Historian Installation Features...........................29
Installing the IndustrialSQL Server Historian Program Files...............30
Configuring Databases and Data File Locations...................................38
Testing the Installation ..........................................................................42
Repairing the IndustrialSQL Server Historian......................................42
Modifying the IndustrialSQL Server Historian Installation .................44
Removing the IndustrialSQL Server Historian .....................................47
IndustrialSQL Server Historian Menu Shortcuts ..................................50

CHAPTER 3: Upgrading from a Previous

Version ...............................................................51
About Upgrading to the IndustrialSQL Server 9.0 Historian ...............51
About Database Migration ................................................................51
Upgrading from a Previous Version......................................................52
Migration of History Data Stored in SQL Server..............................54
Upgrading from Microsoft SQL Server 7.0 ......................................56
Upgrading the IndustrialSQL Server Historian to a Different
Computer...............................................................................................57

APPENDIX A: System Sizing Examples.........59

Server 1: P4 3.2 GHz Single Processor.................................................59
Server 2: P4 3.0 GHz Dual Processor ...................................................60
Server 3: P4 2.7 GHz Xeon Quadruple Processor ................................62

Index ..................................................................65

IndustrialSQL Server Historian Installation Guide

 Before You Begin 5

Before You Begin

About this Guide

This IndustrialSQL Server™ Historian Installation Guide provides
information on installing the IndustrialSQL Server historian, including
hardware and software requirements and upgrade instructions.
The IndustrialSQL Server historian is tightly integrated with Microsoft
products, and working knowledge of both Microsoft SQL Server and
Microsoft Windows operating systems is required.
For more information on Microsoft SQL Server or Windows operating
systems, see your Microsoft documentation.

IndustrialSQL Server Documentation Set

The IndustrialSQL Server historian documentation set includes the following
guides:
• IndustrialSQL Server Historian Installation Guide. This guide provides
information on installing the IndustrialSQL Server historian, including
hardware and software requirements and migration instructions.
• IndustrialSQL Server Historian Concepts Guide. This guide provides an
overview of the entire IndustrialSQL Server system and describes each of
the subsystems in detail.
• IndustrialSQL Server Historian Administration Guide. This guide
describes how to administer and maintain an installed IndustrialSQL
Server historian, such as configuring data acquisition and storage,
managing security, and monitoring the system.
• IndustrialSQL Server Historian Database Reference. This guide provides
documentation for all of the IndustrialSQL Server database entities, such
as tables, views, and stored procedures.
• IndustrialSQL Server Historian Enterprise Edition User’s Guide. This
guide describes IndustrialSQL Server failover clustering and provides
details on how to plan, configure, implement, and manage the
IndustrialSQL Server Enterprise historian.
• IndustrialSQL Server Historian Glossary. This guide provides definitions
for terms used throughout the documentation set.
A PDF file for each of these guides is available on the IndustrialSQL Server
historian installation CD. You can easily print information from the PDF files.
The IndustrialSQL Server historian documentation is also provided as an
online Help file, which can be accessed from the System Management Console
management tool.

IndustrialSQL Server Historian Installation Guide

6 Before You Begin

Document Conventions
This documentation uses the following conventions:

Convention Used for

Initial Capitals Paths and filenames.
Bold Menus, commands, dialog box names, and dialog box
options.
Monospace Code samples and display text.

IndustrialSQL Server Historian Installation Guide

 Requirements and Recommendations 7

C H A P T E R 1

Requirements and
Recommendations

For your IndustrialSQL Server historian to achieve maximum performance,

make sure your hardware and software meets the following requirements.
Because the IndustrialSQL Server historian is a high-performance relational
database, it is also important to size your system to handle the level of input
that you expect to store.

Contents
• Server Requirements
• Requirements for Historian Management Tools
• Remote IDAS Requirements
• Disk Sizing and Data Storage
• Performance Considerations
• Networking Recommendations
• Client Access
• Licensing
• Support for Non-English Operating Systems
• Integration with Other Wonderware Products
• Anti-Virus Software

Server Requirements
The minimum hardware and software requirements for the IndustrialSQL
Server historian are based on the tag count and the anticipated data throughput
rate. These requirements are divided into four levels, which are outlined in this
section.
The recommended memory configuration for SQL Server 2000 is to clamp its
memory consumption to 50% of the amount of physical memory installed on
the server or 512 MB, whichever is smaller. The recommended Windows
virtual memory setting is twice the amount of physical RAM installed on the
server.

IndustrialSQL Server Historian Installation Guide

8 Chapter 1

For tag counts less than 30,000, the data throughput rate is assumed to be equal
to the tag count. For tag counts greater than or equal to 30,000, the data
throughput rate is assumed to be 30,000 values per second. This is the
guaranteed throughput that the system can handle, but throughput rates
subbstantially higher are possible, depending on hardware configuration.

Note If the IndustrialSQL Server historian is running on the Windows Server

2003 operating system, DDE is not supported.

Level 1 Server
A Level 1 server can handle a load of about 5,000 tags. For example, 2,600
analogs, 2,200 discretes, 300 strings, and 20 non-I/O Server (manual) tags. The
minimum requirements are:
• P4 3.2 GHz CPU
• Any of the following operating systems:
• Windows 2000 Professional SP4
• Windows XP Professional SP2
• Windows 2000 Server SP4
• Windows 2000 Advanced Server SP4
• Windows Server 2003 Standard Edition
• 1 GB RAM
• 1 GB network interface card (NIC)
• Microsoft SQL Server 2000 Standard Edition SP3a
OR
Microsoft SQL Server 2000 Personal Edition SP3a, which is required for
Windows 2000 Professional and Windows XP Professional
• 270 MB of free disk space to install the IndustrialSQL Server historian
Level 2 Server
A Level 2 server can handle a load of about 63,000 tags. For example, 40,000
analogs, 20,000 discretes, 300 strings, and 5,000 non-I/O Server (manual) tags.
The minimum requirements are:
• P4 3.0 GHz Dual CPU
• Any of the following operating systems:
• Windows 2000 Professional SP4
• Windows XP Professional SP2
• Windows 2000 Server SP4
• Windows 2000 Advanced Server SP4
• Windows Server 2003 Standard Edition
• 1 GB RAM
• 1 GB network interface card (NIC)

IndustrialSQL Server Historian Installation Guide

 Requirements and Recommendations 9

• Microsoft SQL Server 2000 Standard Edition SP3a

OR
Microsoft SQL Server 2000 Personal Edition SP3a, which is required for
Windows 2000 Professional and Windows XP Professional
• 270 MB of free disk space to install the IndustrialSQL Server historian
Level 3 Server
A Level 3 server can handle a load of 130,000 tags. For example, 70,000
analogs, 50,000 discretes, 6,000 strings, and 20 non-I/O Server (manual) tags.
The minimum requirements are:
• P4 2.7 GHz Xeon Quad
• Any of the following operating systems:
• Windows 2000 Server SP4
• Windows 2000 Advanced Server SP4
• Windows 2003 Standard Server
• Windows Server 2003 Enterprise Edition
• 8 GB RAM
• 1 GB network interface card
• Microsoft SQL Server 2000 Standard Edition SP3a
• 270 MB of free disk space to install the IndustrialSQL Server historian
A performance report for different historian systems is provided in Appendix
A, "System Sizing Examples."

High Availability Support

The IndustrialSQL Server historian provides built-in support for Stratus ft3500
fault-tolerant servers and for Microsoft dual-node, active/passive failover
clusters.

Requirements for Historian Management Tools

The management tools include the IndustrialSQL Server System Management
Console and the InSQL Database Export/Import Utility. If you are installing
the tools on a remote computer, the following requirements apply:
• Any of the following operating systems:
• Windows XP Professional SP2
• Windows 2000 Professional SP4
• Windows 2000 Server SP4
• Windows 2000 Advanced Server SP4
• Windows Server 2003 Standard Edition
• Windows Server 2003 Enterprise Edition

IndustrialSQL Server Historian Installation Guide

10 Chapter 1

• Microsoft Management Console 2.0

• MDAC 2.7
• Internet Explorer 5.5 or later
• 20 MB of free disk space

Note The InTouch History Importer is installed as part of a server installation.

Remote IDAS Requirements

A remote IDAS can run on the following operating systems:
• Windows XP Professional SP2
• Windows 2000 Professional SP4
• Windows 2000 Server SP4
• Windows Server 2003 Standard Edition
• Windows Server 2003 Enterprise Edition
A remote IDAS runs on all possible server and workstation roles defined by
the Windows XP, Windows 2000, or Windows 2003 operating systems:
domain member, standalone workstation, or server.
To determine the CPU and memory needed for a remote IDAS, use the same
guidelines as for the IndustrialSQL Server historian computer. For more
information, see "Server Requirements" on page 7.
The IDAS computer does not need to be quite as powerful as the server
computer, because it will not be performing all of the same functions (for
example, processing SQL Server transactions), but it should be powerful
enough to handle the tag load that you expect.
The amount of free disk space required depends on whether or not you will
have store-and-forward enabled for the IDAS. If store-and-forward is enabled,
you need to make sure that the disk space on the remote IDAS computer is
sufficient to store cached data if the network connection to the historian fails.
Estimate the disk space requirements for a remote IDAS the same as for the
historian. For more information, see "Disk Requirements for Historical Data
Files" on page 14.
A remote IDAS configured for store-and-forward also has more stringent
requirements on memory to ensure that the IDAS local storage engine has
sufficient resources to run properly. In general, size memory for a remote
IDAS configured for store-and-forward the same as you would for a historian
having the corresponding tag count.

IndustrialSQL Server Historian Installation Guide

 Requirements and Recommendations 11

Security Considerations for a Remote IDAS

If you set up a remote IDAS, you need to configure security settings that allow
access permissions between the remote IDAS and the IndustrialSQL Server
historian. For example, the historian needs to access the remote computer to
start and stop the IDAS. Also, the remote IDAS needs to access the historian
computer to send data. These are administrative tasks, which require
administrative permissions.
When you install the historian, you must specify an administrative user
account under which all of the historian services run. Make sure that this same
user account is added to the Administrators security group on the remote IDAS
computer. The existence of the same administrative user account on both
computers allows the historian to access the remote IDAS, and vice-versa.

Note A remote IDAS only requires the same administrative account to exist
on the local computer and the historian. It is not necessary for you to log in to
the remote IDAS computer using the administrator account.

After installing the historian, if you change the Windows login using the
System Management Console, make sure that the user account change is
reflected on the remote IDAS computer.
If you are running the historian in a domain environment (recommended), you
can create the administrative user account on the domain controller and simply
add the account to the Administrators group on the historian computer and the
remote IDAS computer. Do not create a local user on any computer with the
same name and/or password as this administrative user account.
If you are running a remote IDAS in a workgroup environment, there is no
centralized management and authentication of user accounts (no domain
controller). Create the same administrative user account on each individual
computer running a historian component. For example, if you have a computer
running the historian and plan to install remote IDASs on two other computers,
create the user account (that is, matching usernames and passwords) on all
three computers.
For information on workgroups, domains, creating user accounts, and adding
accounts to the Administrators security group, see your Microsoft operating
system documentation.

Disk Sizing and Data Storage

A number of storage-related questions must be answered when setting up the
IndustrialSQL Server historian. They include:
1. How important is the data? Is it acceptable that four weeks of data is
stored online and is then over-written?
2. How important is the configuration and event data? This type of
information is stored in the Microsoft SQL Server database.
3. How often is data in the Microsoft SQL Server database changing?
4. Is anyone in the organization going to require operating data that is older
than a month? Older than a year?

IndustrialSQL Server Historian Installation Guide

12 Chapter 1

5. How much is the SQL Server component of the historian expected to be

used (for example, for the event system)?
6. How long can the system be off-line in the event of a component failure?
7. What happens if the system stops storing data?
8. What happens if stored data is lost as a result of a hard drive failure?
9. Can the server equipment be taken off-line to perform repairs?
Ask yourself questions like these to help you determine your disk space
requirements and how you should plan to protect your data.
A performance report for different historian systems is provided in Appendix
A, "System Sizing Examples."

General Hardware Recommendations for Storage

The following are general recommendations for the hardware used for storage:
• SCSI drives configured using hardware RAID is optimum. The disk space
required is a function of data rate and the desired history duration.
• NTFS is the only officially supported file system for a production
environment. Although the historian will run if you are using the FAT file
system, data corruption may occur if the system crashes while files are
still open.
• Enable file compression for the historical data storage locations: Circular,
Buffer, and Permanent. File compression on these directories is
automatically set during the installation process. However, if you re-assign
the storage locations (for example, for the alternate location), you must set
the compression manually.

Note File compression is only available for the NTFS file system.

Planning for Disk Space Requirements

There are four factors to consider when estimating the amount of disk space
required to run the IndustrialSQL Server historian:
• Disk space required to install the required software components and files
needed to run the historian.
• Disk space required to store the historian database files.
• Disk space required to store the historical data files.
• If a remote IDAS is used, the disk space required on the local IDAS
computer to store cached data if the network connection to the historian
fails.
A performance report for different historian systems is provided in Appendix
A, "System Sizing Examples."

IndustrialSQL Server Historian Installation Guide

 Requirements and Recommendations 13

Disk Requirements for Software Components

The following table describes the minimum disk space required to install the
software (besides the operating system) for an IndustrialSQL Server historian.

Minimum Disk
Software Space Required
Microsoft SQL Server See your Microsoft
documentation.
Common Component Files 20 MB or less
IndustrialSQL Server historian program files, 18 MB
including the System Management Console tool
and documentation files.
System Management Console only 10 MB
Remote IDAS only 4 MB

Disk Requirements for Database Files

The IndustrialSQL Server historian installation program adds two databases to
the Microsoft SQL Server: Runtime and Holding.
• The Runtime database stores all historian configuration data and event
data. The information in the Runtime database is stored to disk as a
database file named Run90dat.mdf. Its associated log file is Run90log.ldf.
The configuration data in the database file remains relatively static and
usually never causes the file size to go above 20 MB. However, if you set
up events, records of event detections and the results of any data
summaries or snapshots increase the size of the Runtime database file
because the tables are filling up. Also, entries are created in the log file for
event-related transactions. If the database files are set to auto-size, the
Runtime database file expands to accommodate event-related data until
the hard drive is full.
• The Holding database temporarily stores tag definitions being imported
from InTouch® HMI software. The information in the Holding database is
stored to a database file named Holding90Dat.mdf. Its associated log file
is Holding90Log.ldf.

Note Historical plant data is not stored in the database files. This type of data
is stored in special files called history blocks.

The minimum disk space for the database files is as follows:

File Size
Runtime database file 30 MB
Runtime log file 10 MB
Holding database file 30 MB
Holding log file 10 MB
Total Space Used (Minimum) 80 MB

IndustrialSQL Server Historian Installation Guide

14 Chapter 1

The Runtime and Holding databases are set to automatically expand at a 10%
rate (the default).
You cannot change these defaults during the installation. The databases can be
resized later using Microsoft SQL Server utilities. For more information on
sizing databases, see your Microsoft SQL Server documentation for guidelines.

Note If you are upgrading version 7.1 or 8.0 of the IndustrialSQL Server
historian, the installation program needs space to save a copy of the old
Runtime database while it creates the new one. To upgrade, the database space
required is twice the size of the old database, plus the database size for the new
install.

Disk Requirements for Historical Data Files

The IndustrialSQL Server historian stores historical plant data to hard disk in
special files called history blocks. When you install the historian, you are
required to specify a storage location (directory) in which these files will be
dynamically created and subsequently filled. You must have at least 200 MB of
free disk space for these files to install the historian.
After the historian is up and running, when the free space on the drive
containing the storage directory drops below a minimum threshold, the oldest
data is overwritten. It is very important that you allocate enough disk space for
storing your plant data for the desired length of time.
The amount of data that can be stored to disk before running out of space is
dependent upon the number of tag values that are stored and how often they are
stored. That is, the more tags you have, the fewer values you can store per tag
before you need to archive off the oldest data. Likewise, the higher the
specified storage rate per tag, the faster the system runs out of space.
NTFS file compression can reduce the actual amount of storage space by
factors of 2:1 to 10:1. For the estimates, a conservative "worst case" factor of
2:1 is used.

Important! You must have sufficient disk space in the circular storage area to
hold at least two full history blocks, plus the space specified for the minimum
threshold for the circular storage area. Use the System Management Console to
view or change the minimum threshold value.

A performance report for different historian systems is provided in Appendix

A, "System Sizing Examples."

IndustrialSQL Server Historian Installation Guide

 Requirements and Recommendations 15

Analog, Discrete, and Fixed-Length String

Storage Requirements
For analog, discrete, and fixed-length string (128 characters or less) tags, each
value that is stored uses Storage Size + 3 bytes of disk space, plus
approximately 15% overhead. Use the following formula to estimate the disk
usage:
Estimated disk usage per day = (1.15*(Storage Size + 3)*number of tags)
* (60/storage rate in seconds) * 60 minutes * 24 hours / (NTFS
compression ratio)
For example, the disk usage per day for 10,000 4-byte analog tags (that is,
Storage Size = 4 bytes) that are stored at ten-second intervals would be
(1.15*(4+3)*10000)*(60/10)*60*24/2, which is approximately 332 MB per
day.
The disk usage per day for 10,000 discrete tags (that is, Storage Size = 1 byte)
that are changing, on average, every 60 seconds would be
(1.15*(1+3)*10000)*(60/60)*60*24/2, which is approximately 32 MB per
day.
The disk usage per day for 10,000 8-byte string tags (that is, Storage Size = 8
bytes) that are changing, on average, every 60 seconds would be
(1.15*(8+3)*10000)*(60/60)*60*24/2, which is approximately 87 MB per
day.

Variable-Length String Storage Requirements

For strings of variable length that are 128 characters or more, the number of
bytes required for storage will be the actual number of characters being sent
from the data source + 5 bytes, plus 15% overhead. Therefore, the average disk
usage per day for a variable-length string that is receiving an average of 'N'
characters per sample could be calculated using the following formula:
Estimated average disk usage per day = (1.15 *(N+5)*number of tags) *
(60/average storage rate in seconds) * 60 minutes * 24 hours / (NTFS
compression ratio)
For example, the disk usage per day for 10,000 131-byte string tags that are
changing, on average, every 60 seconds and the average incoming value is 60
characters in length would be (1.15*(60+5)*10000)*(60/60)*60*24/2, which
is approximately 513 MB per day.
The use of variable-length strings also has an impact on memory. For more
information, see see "Automatic Resizing of the Active Image" in Chapter 5,
"Data Storage Subsystem," in your IndustrialSQL Server™ Historian
Concepts Guide.

Performance Considerations
For a complete IndustrialSQL Server historian system, the following
components put a demand on memory.
• Internal historian subsystems, such as the Configuration Manager, data
acquisition, and data storage

IndustrialSQL Server Historian Installation Guide

16 Chapter 1

• The associated Microsoft SQL Server

• The operating system
• Client access (data retrieval), which includes caching
When determining the amount of memory to purchase, remember that adding
more memory is the cheapest and easiest thing that you can do to improve
performance. Increasing the amount of memory reduces the amount the server
has to use virtual memory, thus lowering the load on the storage subsystem.
Even if you have a large amount of memory, additional memory is used as
additional disk cache, speeding up disk access and therefore file service. Also,
processes needed by the server become faster because they are memory-
resident.
A major factor in system performance is the amount of plant data you
anticipate storing in the system, including considerations about how often that
data is stored and retrieved. In general, the more you store, the more often you
store it, and the more you retrieve it, the slower the system. Major storage
factors affecting the performance of the system are:
• Effective analog flow rate (analog updates per second).
• Period of online data storage required.
• Effective discrete variable flow rate.
• Number of concurrent end users required.
• Complexity of end user queries.
• Number and size of string tags, as well as the effective flow rate of string
values.
• Number and duration of string tag retrieval queries, as well as the
frequency at which these queries are executed.
A performance report for different historian systems is provided in Appendix
A, "System Sizing Examples."

Server Loading
When a user connects to the IndustrialSQL Server historian with a client,
configuration information is immediately requested from the historian. This
information includes the tags that the server is storing, their descriptions,
engineering units, and so on. SQL Server reads this information from the
database (stored on disk) and places it in memory.
As the user selects time periods to trend, for example, the historian reads data
from files located on the disk and prepares the results of the client's data
request to be transmitted back to the client. The ability of the server to quickly
handle subsequent requests for data from the same client and others is
dependent on the server's ability to keep as much information in memory
without having to again access data from the disk.
As a higher load is placed for memory, a higher load is placed on the disk I/O
system as the server has to use disk caching and read from the data files.

IndustrialSQL Server Historian Installation Guide

 Requirements and Recommendations 17

The following table summarizes the loading for various systems.

System Load Description

Acquisition and Base load of the historian. This load exists as long as the
storage system is running. However, this load is not affected by
client activity.
Retrieval Variable loading caused by data retrieval from client
applications. When the client initially connects, the data
requested is configuration data, which is stored in SQL
Server. The historian requests data from SQL Server,
causing its loading to increase. As the client requests
historical data, the disk time increases as information
from the data files is transferred to memory. This
continues as the client requests additional data. If the
client application requests data that has already been
transferred to memory, there is no associated disk
activity and transfer of data to memory.

The server must be able to adequately handle the variation on loading caused
by the client applications. To accomplish this, make sure that your hardware is
sized so that it can handle the base load created by the acquisition and storage
systems and that there are adequate resources still available for the retrieval
system.

IDAS Performance
An IDAS can acquire an unlimited number of real-time data values, from an
unlimited number of I/O Servers, each with an unlimited number of topics.
However, IDASs are subject to the following limitations.
• The maximum sustained data throughput for any single IDAS is 30,000
items per second for real-time data. For late or old data, the maximum
throughput is 9,000 items per second. The total combined throughput
(real-time data plus late or old data) cannot exceed 30,000 items per
second. For higher-volume applications, you can set up multiple IDASs to
serve a single storage subsystem.
• The size of any data value is limited to 64,000 bytes.
• The maximum number of tags supported by any single IDAS is 30,000.

Storage Subsystem Performance

The storage subsystem can support a continuous data acquisition rate of 30,000
updates per second. The storage sub-system also supports a burst rate of
60,000 updates per second for up to 1 second.
The storage subsystem processes all real-time data as a high-priority task that
is never interrupted. However, data received via "manual" methods (such as
UPDATE/INSERT commands, CSV file imports, store-and-forward, and so
on) is handled by a low priority task. If the system is generally busy, then it
may take some time for the manual data to be posted.

IndustrialSQL Server Historian Installation Guide

18 Chapter 1

Networking Recommendations
The IndustrialSQL Server historian is a highly configurable package that can
be set up in many different ways depending on your needs.
The historian can use any protocol currently supported by Microsoft SQL
Server 2000. You can use the default Microsoft SQL Server 2000 protocol
(named pipes) with TCP/IP. TCP/IP is required if SuiteLink™ is used.

Note If the historian is running on the Windows Server 2003 operating

system, DDE is not supported.

It is highly recommended that you run the historian on a dedicated computer.

For example:
• Do not use the historian computer as a domain controller, mail server,
Internet server, and so on.
• Do not use the historian computer as a workstation.
• Do not use the historian computer for InTouch HMI software, InControl™
software, and so on.
Generally, it is recommended that you split the process and IS networks to
ensure that the process network does not become overloaded. The following
illustration shows one possible network architecture where the historian is the
link between the process network and the business LAN/WAN:

&OLHQW &OLHQW &OLHQW

/$1:$1

2SHUDWRU6WDWLRQ

,QGXVWULDO64/6HUYHU %XVLQHVV6HUYHU

,Q7RXFK
3ODQW1HWZRUN

,Q&RQWURO'DWD$FTXLVLWLRQ3/&V'&6V3URFHVV&RPSXWHUV,QVWUXPHQWV

For this architecture, install two network cards on a server computer and
configure them to segment the IS network from the process network.

IndustrialSQL Server Historian Installation Guide

 Requirements and Recommendations 19

Note All tags to be stored in historian are on "advise" all of the time. This
may cause heavy load conditions on the process network. Before you install
the historian, investigate the possible load impact of installing the historian on
your network.

Client Access
All clients should connect to the IndustrialSQL Server historian using the
default Microsoft SQL Server connection. Usually, this means using the name
of the computer on which the historian is running as the server name when
logging on.

Client Connections to the IndustrialSQL Server

Historian
The IndustrialSQL Server historian and its clients consume both Windows
operating system connections and SQL Server connections in the following
ways:
• IndustrialSQL Server historian: When the historian itself is running
without the event subsystem, it uses six database connections and zero
Windows connections.
• System Management Console: Each open System Management Console
consumes one database connection, and each remote System Management
Console also consumes a Windows connection.
• Event System: Each different time interval for event tags uses a database
connection and zero Windows connections. For example, if there are 15
event tags with time interval of 30 minutes, and 10 event tags with an
interval of 60 minutes, that consumes two connections. The event
subsystem uses zero Windows connections.
• Local IDAS: Consumes no connections.
• Remote IDAS: Each remote IDAS uses one Windows connection and
zero database connections.
• Industrial Application Server Platform: A Platform configured to
historize data consumes a Windows connection and a database connection.
Local Platforms on the historian node are not supported.
• Industrial Application Server Engine: Each Engine configured to
historize data will consume a database connection.
• ActiveFactory clients and control: Each ActiveFactory client or control
will consume a database connection for each specified server, and each
remote node consumes a Windows connection.
Certain versions of the operating system and SQL Server impose connection
limits or workload limits. For more information, see "Client Connection and
Workload Limits" on page 20.

IndustrialSQL Server Historian Installation Guide

20 Chapter 1

Client Connection and Workload Limits

Small historian applications can use an IndustrialSQL Server historian that is
running on Windows 2000 Professional or Windows XP Professional.
However, only small applications are supported because of the performance
limitations imposed by the operating system and by Microsoft SQL Server.
• Operating System Limitations
Microsoft limits the number of concurrent client connections to the
"desktop" versions of their operating systems. For Windows, a
"connection" is access to any service on the computer (for example, file
sharing, print services, Terminal Services, remote access, authentication,
and any connection through a named pipe). These connections are specific
to the client computer, so if NodeA is accessing print services and a shared
directory on NodeB, that counts as a single connection to NodeB.
The Professional operating systems reject all connections above the 10-
connection limit. More details on these limits are available in Microsoft
Knowledge Base articles 122920 (Windows 2000 Professional) and
314882 (Windows XP Professional).
• SQL Server Limitations
On the Windows 2000 Professional and Windows XP Professional
operating systems, the historian uses Microsoft SQL Server Personal
Edition, rather than the Standard Edition or Enterprise Edition used on the
Windows 2000 Server and Windows Server 2003 operating systems.
SQL Server 2000 Personal Edition contains a workload governor that
limits performance if the database receives more work than is typical of a
small number of users. This governor controls the number of concurrently
executing "batches" (queries) against the SQL Server. For the historian,
the most likely sources for concurrent batches are event subsystem queries
and ActiveFactory trends running in "live" mode. For mor information on
the workload governor, see the Microsoft documentation.

Note SQL Server Personal Edition also has database size limitations, but
these are sufficiently high enough that they do not impact historian
operation.

In deciding whether a Professional operating system or the Personal Edition of

SQL Server are suitable for a given application, you need to clearly understand
how the historian and its clients consume connections. For more information,
see "Client Connections to the IndustrialSQL Server Historian" on page 19.
The historian running on the Windows 2000 Professional or Windows XP
Professional operating system has the exact same FactorySuite Client Access
License (FSCAL) requirements as the historian running on a server operating
system: either all clients accessing the historian need a "per seat" FSCAL, or
each processor in the historian needs a "per processor" FSCAL.

IndustrialSQL Server Historian Installation Guide

 Requirements and Recommendations 21

Network Protocols for Clients

To change the default network protocol used by Microsoft SQL Server to
something other than named pipes, configure the client network access using
the SQL Server Client Network Utility. For more information, see your
Microsoft SQL Server documentation.

Licensing
The IndustrialSQL Server historian requires a valid license to run. Use the
ArchestrA License Utility to manage licenses and associated feature lines.
The historian allows functionality based on the presence of a valid license file
and/or feature lines. The historian checks that:
• A valid license file exists the expected location on disk.
• One or more feature lines relevant to the product is contained in the
license file. A feature line defines specific behavior that is allowed for the
product. Typically, feature lines are bundled together according to pre-
defined licensing schemes.
If a valid license file cannot be found, or if the file does not contain the
appropriate feature lines, the historian is considered to be unlicensed. If
unlicensed, the historian starts up and runs for an unlimited period of time.
However, data is only collected and stored for system tags.
The historian reads the license file and appropriately updates the system
behavior when:
• The historian starts up.
• You commit changes to the system using the System Management
Console.
• You refresh the license information using the System Management
Console.
Unless otherwise noted, all aspects of historian licensing are dynamic.That is,
you can make licensing changes during runtime, and the system runs
interrupted.
The following feature lines are available:
• Historian_Tagcount Feature Line
• Historian_MSCluster Feature Line
• Historian_ServerOS Feature Line
• Historian_RemoteIDASCount Feature Line
• Historian_ModifyHistoryData Feature Line
• Historian_HistoryDuration Feature Line
• Historian_Processors Feature Line

IndustrialSQL Server Historian Installation Guide

22 Chapter 1

Use the System Management Console to view license and feature line
information relevant to the historian. For more information, see "Viewing
License Information" in Chapter 8, "Viewing or Changing System-Wide
Properties," in your IndustrialSQL Server™ Historian Administration Guide.

Historian_Tagcount Feature Line

The Historian_Tagcount feature line specifies the number of tags for which the
IndustrialSQL Server historian acquires and stores data. The tag count feature
line does not restrict the number of tag definitions you can create in the
database, just the tags for which data is acquired and stored. System tags and
event tags are not included in the tag count.
If this feature line is absent, or if no license file is found, tag count defaults to
0.
For a licensed tag count of n, the historian recognizes only the first n non-
system tags it reads from the database, in whatever order the database presents
the tags to the InSQLConfiguration service. For example, if you have a
licensed tag count of 500, only the first 500 non-system tags are licensed for
data collection and storage.
If the tag count feature line in the license file changes, the runtime behavior of
the historian does not change until you refresh the license information or a
system restart occurs. If the tag count is increased, the historian starts acquiring
and storing data for the additional tags, if they exist in the database. If the tag
count is decreased, the historian stops acquiring and storing data for all tags
except for the system tags and the first n tags in its list, where n denotes the tag
count.

Historian_MSCluster Feature Line

The Historian_MSCluster feature line controls whether the installed version of
the IndustrialSQL Server historian is licensed to run on a Microsoft failover
cluster.
If the historian is installed on a cluster system, and this feature line is present in
the license file, the historian runs with full cluster functionality, in addition to
the functionality as defined by the other feature lines in the license file. If the
feature line is not found, the behavior is the same as for the regular version of
the historian running as unlicensed.

Historian_ServerOS Feature Line

The Historian_ServerOS feature line controls whether the installed version of
the IndustrialSQL Server historian is licensed to run on one of the following
Microsoft server operating systems:
• Microsoft Windows 2000 Server
• Microsoft Windows 2000 Advanced Server
• Microsoft Windows 2000 Datacenter Server
• Microsoft Windows 2003 Standard Edition

IndustrialSQL Server Historian Installation Guide

 Requirements and Recommendations 23

• Microsoft Windows 2003 Enterprise Edition (in a non-clustered

configuration)
• Microsoft Windows 2003 Datacenter Edition (in a non-clustered
configuration)
If any of the server operating systems are included in a clustered
configuration, the Historian_MSCluster feature line is required, instead of the
Historian_ServerOS feature line.
If the historian is installed on a server operating system, and this feature line is
present in the license file, the historian runs with full functionality as defined
by the other feature lines in the license file. If the feature line is not found, the
behavior is the same as for the regular version of the historian running as
unlicensed.
This feature line has no effect if the historian runs on a non-server operating
system or in a clustered environment.

Historian_RemoteIDASCount Feature Line

The Historian_RemoteIDASCount feature line controls the maximum number
of remote IDASs that can be used by the historian. The remote IDAS count
feature line does not restrict the number of remote IDAS definitions you can
create in the database.
If this feature line is 0, then there is no limit on the number of remote IDASs. If
the remote IDAS count feature line does not exist, or if the license file is not
found, no remote IDASs are allowed.
If the remote IDAS count is n, the historian uses the local IDAS, plus the first n
remote IDASs defined in the historian database. The local IDAS is identified
as the IDAS having the same computer name as the historian computer. For
example, if the feature line is equal to 2, then the local IDAS and the first two
defined remote IDASs are used. Any remaining remote IDASs defined in the
database (plus all I/O Servers, topics, and tags associated with these IDASs)
are ignored. Information pertaining to an unlicensed remote IDAS (including
corresponding I/O Servers and topics) does not appear in the System
Management Console.
The tag count feature line is applied after the remote IDAS feature line. If the
license file allows all remote IDASs defined in the database to be used, but not
all of the tags in the database, the historian uses all IDASs, including their
associated I/O Servers and topics, but only acquires and stores data for the
allowed number of tags.
If the remote IDAS count feature line in the license file changes, the runtime
behavior of the historian does not change until you refresh the license
information or a system restart occurs. If the remote IDAS count is increased,
the historian starts acquiring and storing data from the additional remote
IDASs, if they exist in the database. If the remote IDAS count is decreased, the
historian stops acquiring and storing data for all tags assigned to defined
remote IDAS n+1 and higher, where n denotes the remote IDAS count.
For the IDAS failover feature, the remote IDAS count is applied as follows:

IndustrialSQL Server Historian Installation Guide

24 Chapter 1

• The local IDAS is counted only once, even if it has a failover node
configured. At runtime, the failover IDAS (which must be on a remote
node), does NOT run unless a valid license for at least one remote IDAS is
present.
• Each remote IDAS configured in the database is counted only once, even
if it has a failover node configured.

Historian_ModifyHistoryData Feature Line

The Historian_ModifyHistoryData feature line controls whether history data
modifications are allowed.
The data modification feature line controls whether you can modify history
data via SQL queries (inserts or updates) and CSV file imports (both normal
CSV imports and "fast load" CSV imports).
• If the feature line is present, all CSV file import operations, as well as
SQL inserts and updates, are permitted.
• If the feature line is not detected, all attempted operations involving SQL
inserts and updates and CSV file imports (including FastLoad) are not
allowed.
If disallowed, SQL insert queries and update queries return an appropriate
message to the client stating that the license excludes this functionality. For
CSV file imports and fast load file imports, a warning message is logged when
a file is first placed in the historian import folder. The warning message states
that the license excludes this functionality.

Historian_HistoryDuration Feature Line

The Historian_HistoryDuration feature line controls the maximum number of
days in history, starting with the current day, for which data can be retrieved
from the IndustrialSQL Server historian. For example, if the history duration is
50, you can only retrieve data that was stored during the last 50 days.
If this feature line is 0, then there is no limit on retrieving data. If this feature
line is missing, the default is seven days.
If you attempt to retrieve data for a period of time starting before the earliest
time indicated by this feature line, the start time for the data retrieval is reset to
the earliest time allowed by the feature line.
This feature line has no impact on data storage in the IndustrialSQL Server
historian. For information on restricting the amount of data that is stored, see
"Automatic Deletion of History Blocks" in Chapter 5, "Data Storage
Subsystem," in your IndustrialSQL Server™ Historian Concepts Guide.

Historian_Processors Feature Line

The Historian_Processors feature line controls the maximum number of
processors (CPUs) allowed in the IndustrialSQL Server historian computer.
This feature line has no impact on the operation of remote IDASs or other
remote clients of the historian.

IndustrialSQL Server Historian Installation Guide

 Requirements and Recommendations 25

If this feature line is absent, a maximum of one processor is assumed.

If the actual number of processors in the historian computer is less than or
equal to the number of processors specified in the feature line, the historian is
considered to be licensed.
Hyperthreaded CPUs are not supported and not recommended. If the historian
computer is using hyperthreaded CPUs, each hyperthread is included in the
processor count and may cause licensing violations. For example, on a system
with dual hyperthreaded CPUs, the Historian_Processors feature line must be 4
or more. To disable hyperthreading, use the computer BIOS setup program.

Support for Non-English Operating Systems

The English version of IndustrialSQL Server historian, the InSQL Database
Export/Import Utility, and the InTouch History Importer run on the Windows
2000 Server operating system for the following languages. Also, the
corresponding version of Microsoft SQL Server for the required language must
be used.
• German
• French
• Japanese
• Simplified Chinese
The following entities are not supported in double-byte languages:
• Domain names, user names, and passwords (including SQL Server login
names and passwords).
• Names of I/O Server host machines, I/O Server application names, topic
names, and item names.
• Any text associated with licensing.

Integration with Other Wonderware Products

The IndustrialSQL Server historian is Wonderware's open relational database
for plant and process data. Many of the features of the historian allow it to be
used with many of Wonderware's other products.
The historian can store data from any application that supports DDE or
SuiteLink™. Examples of Wonderware applications that can send data to the
historian are Industrial Application Server, I/O Servers, InControl™, and
InTouch® WindowViewer™.

Note If the historian is running on the Windows Server 2003 operating

system, DDE is not supported.

IndustrialSQL Server Historian Installation Guide

26 Chapter 1

Any client application that can retrieve information using SQL can retrieve
data from IndustrialSQL Server. For example, some Wonderware products that
can retrieve data via SQL are the InTouch, SuiteVoyager®, ActiveFactory™,
SPCPro, InTrack™, and InBatch™ products. The historian further extends
SQL to improve the ability to handle time series data. These time domain
extensions are called Industrial-SQL.
Also, InSQL I/O Server (aahIOSvrSvc.exe) is an interface for clients to access
current data values a historian via the DDE or SuiteLink protocol. The InSQL
I/O Server can update items with current values for given topics, providing
"real-time" I/O Server functionality.
Finally, you can use InTouch to configure the historian by importing tag
definitions and I/O Server definitions from the InTouch Tagname.x file into the
Runtime database.

Anti-Virus Software
Some virus scanners lock key files during a scan, and this may interfere with
normal operation of the IndustrialSQL Server historian. Anti-virus software
should not process files in the C:\InSQL folder. (This is the default installation
folder for history data.)
If, during IndustrialSQL Server installation, you choose a different folders, be
sure that you configure the anti-virus software accordingly.

IndustrialSQL Server Historian Installation Guide

 Installation 27

C H A P T E R 2

Installation

A complete IndustrialSQL Server historian system consists of the following

software components:
• Microsoft SQL Server
• Historian program files, database files, and history data files
• System Management Console, the configuration and control tool
• One or more local or remote IDASs (at least one must be defined)
• IndustrialSQL Server historian online Help.
You should have a definite plan for implementing the historian in your plant
environment before you start the installation process. This plan should include
the type of network architecture for the historian system, considerations for
how much disk space is required for data storage, and the amount of space
required for the historian database files and log files.
Also, any administrative security accounts that you specify for either the
Microsoft SQL Server or the historian should be accounts that do not change
often, if ever. In particular, do not change an administrative password during
any part of the installation process.

Note The user that is currently logged on to the local computer must have
administrative rights to install the historian.

The installation program detects any previous versions of the historian and
notifies you of your migration options.

Contents
• Microsoft SQL Server Installation
• About the IndustrialSQL Server Historian Installation
• IndustrialSQL Server Historian Installation Features
• Installing the IndustrialSQL Server Historian Program Files
• Configuring Databases and Data File Locations
• Testing the Installation
• Repairing the IndustrialSQL Server Historian
• Modifying the IndustrialSQL Server Historian Installation

IndustrialSQL Server Historian Installation Guide

28 Chapter 2

• Removing the IndustrialSQL Server Historian

• IndustrialSQL Server Historian Menu Shortcuts

Microsoft SQL Server Installation

The required version of Microsoft SQL Server must be installed and running
before you can install the IndustrialSQL Server historian. A Microsoft SQL
Server installation CD is included in your historian package.
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 SQL Server 2000 Service Pack 3a is required.
• Microsoft Client Utilities must be installed.
• The historian must run with the Microsoft SQL Server default instance
name (that is, the computer name).
• 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, keep in mind that the historian
Runtime database will grow, especially if you will be using 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 sa password for
Microsoft SQL Server.
• 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.

About the IndustrialSQL Server Historian

Installation
The IndustrialSQL Server historian is performed in two phases. In the first
phase, the installation program performs the following operations:

IndustrialSQL Server Historian Installation Guide

 Installation 29

• Deploys the common components, such as SuiteLink and the License

Viewer, unless they are already installed and validated.
• Locates a running Microsoft SQL Server 2000 SP3a on the local
computer.
• Logs on to the installed Microsoft SQL Server using the account of the
person who is currently logged on. This account must be an administrative
account on the local computer.
• Checks for required disk space based on the features that you select.
• Creates the historian directories on the hard disk, installs program files for
the selected features, and registers components. For more information, see
"IndustrialSQL Server Historian Installation Features" on page 29.
• Populates the historian program or startup group with icons.
The Database Configuration Utility automatically runs after the historian
program file installation is complete. This utility:
• Creates and/or configures the required databases.
• Creates the directory for the history data files (history blocks).
• Creates and configures the cluster, if the operating system is configured
for clustering.
For information on implementing an IndustrialSQL Server historian in a
cluster environment, see the IndustrialSQL Server™ Historian Enterprise
Edition User’s Guide.

IndustrialSQL Server Historian Installation

Features
The IndustrialSQL Server historian installation program allows you to install
some of the system features separately. The following table describes the
various historian features that can be installed. The online Help is installed
with all of the features.
For information on hardware and software requirements for installing any of
these features, see Chapter 1, "Requirements and Recommendations."

Feature Description
InSQL Server Installs or re-installs the historian, configuration
tools and utilities, a local IDAS, and ActiveEvent.
IDAS An IDAS, which can be used remotely. The IDAS
is always installed if you select to install a
complete historian.

IndustrialSQL Server Historian Installation Guide

30 Chapter 2

Feature Description
Configuration Tools The server management tools include InSQL
Configuration Editor and InSQL Management
Console. Both of these applications are MMC
snap-ins that are contained in the System
Management Console. These tools are always
installed on the same computer as the historian and
can also be installed on a different computer on the
network. The InSQL Database Export/Import
Utility is also an installed configuration tool.
ActiveEvent ActiveEvent is an ActiveX control that allows you
to notify the historian event system when an event
has occurred in another application, such as
InTouch HMI software.

Installing the IndustrialSQL Server Historian

Program Files
Use the IndustrialSQL Server historian installation program to install the entire
system or any of the features. It is assumed that you are familiar with the
installation options.
The user that is currently logged on must have administrative rights on the
local computer to install the historian.

To install the historian program files

1. Be sure that the Microsoft SQL Server is working properly before you
start the installation.

IndustrialSQL Server Historian Installation Guide

 Installation 31

2. Insert the IndustrialSQL Server CD into your CD-ROM drive. If the setup
program does not automatically run, double-click Setup.exe in the root
directory of the CD. The Welcome dialog box appears.

IndustrialSQL Server Historian Installation Guide

32 Chapter 2

3. Click Next. The License Agreement dialog box appears.

Be sure that you understand the license agreement before installing. You
cannot continue with the installation without consenting to the agreement.
4. To print out the license agreement, click Print License.

IndustrialSQL Server Historian Installation Guide

 Installation 33

5. If you accept the terms of the license agreement, click Yes. The Select
Features dialog box appears.

6. Select the features to install. For more information, see "IndustrialSQL

Server Historian Installation Features" on page 29.
7. Click Browse to specify a different directory for the historian program
files.

IndustrialSQL Server Historian Installation Guide

34 Chapter 2

8. To check the amount of disk space required for the installation, click Disk
Cost.
If you do not have the required prerequisites for the feature(s) that you
want to install, the Prerequisite Software dialog box appears. Otherwise,
skip to Step 11.

9. Click Exit Install to cancel the IndustrialSQL Server installation.

10. Install the prerequisite(s) and then start the IndustrialSQL Server
installation again.

IndustrialSQL Server Historian Installation Guide

 Installation 35

11. Click Next. If the historian is the first ArchestrA application to be

installed on the computer, the User Name and Password dialog box
appears. If not, skip to Step 14.

12. Enter logon parameters for the ArchestrA user account. This account must
have administrative rights on the computer. This account must also have
security privileges to start and stop services and to access the network.
Domain/Machine
Name of the domain in which the user account will be validated. If you are
not using a domain configuration, enter the computer name.
User Name
User name for the logon account.
Password
Password for the logon account.
Confirm Password
(same as password)

Note To change the ArchestrA user account after installation, use the
Change Network Account utility.

13. Click Create Local Account to have a new account created that uses the
credentials you have provided.

IndustrialSQL Server Historian Installation Guide

36 Chapter 2

14. Click Next. The Ready to Install the Application dialog box appears.

Note If you click Next, you cannot go back and change any of the
installation settings during this instance of setup.

15. If you are installing the historian on the Windows XP Professional SP2 or
Windows 2003 SP1 operating system, select the Launch
OSConfiguration Utility check box.
The OS Configuration Utility modifies the security settings of the
Windows XP Professional SP2 or Windows 2003 SP1 operating system to
allow Wonderware products to operate. This utility does not have a user
interface.

IndustrialSQL Server Historian Installation Guide

 Installation 37

16. Click Next to start the installation. The Updating System dialog box
appears.

When all of the files are copied, the final dialog box appears.

IndustrialSQL Server Historian Installation Guide

38 Chapter 2

17. Click Finish.

After the historian installation program completes, the database Configuration
Utility is automatically launched. For information on using this utility, see
"Configuring Databases and Data File Locations" on page 38.
No errors are logged for the program file install.

Configuring Databases and Data File Locations

Use the database Configuration Utility to configure locations for the
IndustrialSQL Server historian database and data files. This utility also creates
the required historian databases and makes any needed changes to the
Microsoft SQL Server databases.
If the historian is installed on a clustered operating system, use this utility to
configure or change the clustering options. For information, see the
IndustrialSQL Server™ Historian Enterprise Edition User’s Guide.
The utility automatically starts at the end of the historian program file
installation. You can also start the utility at any time by running the
aaHistorianCfg.exe file located in the <installation path>\InSQL\Server folder.
If you are installing the historian, Microsoft SQL Server 2000 SP3a must be
installed and running on the local computer. The Configuration Utility
connects to the SQL Server using Windows authentication.

IndustrialSQL Server Historian Installation Guide

 Installation 39

To configure the databases and data file folders

1. Run the Configuration Utility. The utility checks for an existing Runtime
database. If found, a confirmation dialog box appears.

2. Click Yes to delete the existing Runtime database and create a new
Runtime database. The Configure IndustrialSQL Server database
folder dialog box appears.
If you click No, the existing Runtime database is used, as well as the
existing folder location for the history files. Skip to Step 6.

3. Click Browse to specify a different directory to which to install the

historian database files.
Unless you have specific requirements, keep the default SQL Server
database path. This is the path where the configuration database are
deployed.

IndustrialSQL Server Historian Installation Guide

40 Chapter 2

4. Click Next. The Configure IndustrialSQL Server data directory folder

dialog box appears.

5. Click Browse to specify a different directory for the historian history data
files.
Be sure that you have a sufficient amount of available space on the drive
you specify, as this is where the plant data will be stored.

IndustrialSQL Server Historian Installation Guide

 Installation 41

6. Click Finish. The Processing SQL Script dialog box appears, in which
you can see the historian database configuration scripts running. Multiple
scripts run during the configuration.

At the end of the configuration, the final dialog box appears.

IndustrialSQL Server Historian Installation Guide

42 Chapter 2

7. Click Finish. You may be required to reboot the computer.

8. Read the ReadMe file before using the historian.
The Database Configuration utility logs selected options and outputs messages
to the following location:
..\Documents and Settings\All Users\Application
Data\ArchestrA\Historian\Install\HistorianCfg.txt

Testing the Installation

Test the IndustrialSQL Server historian installation to make sure that
everything is installed correctly and is working properly.

To test the installation:

1. Start up the historian.
2. Start up the storage system and check to see that the system is receiving
data from the system tags.
After the historian is installed, no additional configuration is required to run
client tools against the server using named pipes. However, you may want to
change the system or server configuration using the System Management
Console.

Repairing the IndustrialSQL Server Historian

For a repair, the installation program automatically detects if you have an
existing copy of the IndustrialSQL Server historian on your computer and then
reinstalls missing or corrupt program files, registery keys, and shortcuts.
To repair a database, use the Database Configuration Utility. For more
information, see "Configuring Databases and Data File Locations" on page 38.

To repair the IndustrialSQL Server historian

1. Insert the IndustrialSQL Server CD into your CD-ROM drive. If the setup
program does not automatically run, double-click Setup.exe in the root
directory of the CD. The Welcome dialog box appears.

IndustrialSQL Server Historian Installation Guide

 Installation 43

2. Click Next. The Application Maintenance dialog box appears.

3. Click Repair.

IndustrialSQL Server Historian Installation Guide

44 Chapter 2

4. Click Next. The Ready to Repair the Application dialog box appears.

5. Click Next. The Updating System dialog box appears, indicating the
progress of the repair operations.
When therepair is complete, the final dialog box appears.
6. Click Finish.

Modifying the IndustrialSQL Server Historian

Installation
You can modify which IndustrialSQL Server historian features are installed.
To modify cluster options or the disk directories for the database files and/or
the history data files (history blocks), use the Database Configuration Utility.
For more information, see "Configuring Databases and Data File Locations"
on page 38.

To modify the IndustrialSQL Server historian installation

1. Insert the IndustrialSQL Server CD into your CD-ROM drive. If the setup
program does not automatically run, double-click Setup.exe in the root
directory of the CD. The Welcome dialog box appears.

IndustrialSQL Server Historian Installation Guide

 Installation 45

2. Click Next. The Application Maintenance dialog box appears.

3. Click Modify.

IndustrialSQL Server Historian Installation Guide

46 Chapter 2

4. Click Next. The Select Features dialog box appears.

5. Click to select or clear the features that you want installed/uninstalled. For
information on the features, see "IndustrialSQL Server Historian
Installation Features" on page 29.

IndustrialSQL Server Historian Installation Guide

 Installation 47

6. Click Next. The Ready to Modify the Application dialog box appears.

7. Read the warnings and then click Next. The Updating System dialog box
appears, indicating the progress of the modification operations. At the end
of the modification, the final dialog box appears.
8. Click Finish.

Removing the IndustrialSQL Server Historian

The IndustrialSQL Server historian uninstall program allows you to remove all
of the historian program files. The Runtime and Holding databases and the
history blocks are not deleted.

To remove the IndustrialSQL Server historian

1. Insert the IndustrialSQL Server with CD into your CD-ROM drive. If the
setup program does not automatically run, double-click Setup.exe in the
root directory of the CD. The Welcome dialog box appears.

IndustrialSQL Server Historian Installation Guide

48 Chapter 2

2. Click Next. The Application Maintenance dialog box appears.

IndustrialSQL Server Historian Installation Guide

 Installation 49

3. Click Remove and then click Next. The Wonderware IndustrialSQL

Server Uninstall dialog box appears.

4. To delete the configuration files (idatacfg_*.dat) created by IDAS and the

Configuration Service, select the Delete historian configuration files
check box.
By default, these configuration files are located in \Documents and
Settings\All Users\Application Data\ArchestrA\Historian\ ....

IndustrialSQL Server Historian Installation Guide

50 Chapter 2

5. Click Next. The Updating System dialog box appears, indicating the
progress of the removal operations.
When the historian is removed, the final dialog box appears.

6. Click Finish.

IndustrialSQL Server Historian Menu Shortcuts

The following Start menu shortcuts are created in the
Start\Programs\Wonderware\IndustrialSQL Server folder.
• Database Configuration Export and Import
• Import InTouch Historical Data
• IndustrialSQL Server
• InSQL Books Online
In addition, the shortcut to the System Management Console appears in the
Start\Programs\Wonderware folder.

Note If you performed a complete historian installation, the System

Management Console is configured so that the local SQL Server is already
registered. However, if you only installed the client tools, the console is empty.

IndustrialSQL Server Historian Installation Guide

 Upgrading from a Previous Version 51

C H A P T E R 3

Upgrading from a Previous

Version

You can upgrade from IndustrialSQL Server historian versions 7.1, 8.0, and 8.0
SPx. Directly upgrading from an IndustrialSQL Server 7.0 historian to the
IndustrialSQL Server 9.0 historian is not supported. Upgrading from the
IndustrialSQL Server 3.0 historian is not supported.

Contents
• About Upgrading to the IndustrialSQL Server 9.0 Historian
• Upgrading from a Previous Version
• Upgrading the IndustrialSQL Server Historian to a Different Computer

About Upgrading to the IndustrialSQL Server

9.0 Historian
You can upgrade from the following historian versions:
• IndustrialSQL Server 8.0, 8.0 SP1, 8.0 SP2, 8.0 SP3, and 8.0 SP3a
• IndustrialSQL Server 7.1
A direct upgrade from a 7.0 historian to a 9.0 historian is not supported. To
upgrade from a 7.0 historian, you will need to first upgrade to the 8.0 historian.
Follow the instructions in the 8.0 historian documentation to perform the
upgrade. Once you have upgraded to the 8.0 historian, then you can upgrade to
the 9.0 historian.
Upgrading from IndustrialSQL Server 3.0 is not supported.

About Database Migration

The data in the existing Runtime can be migrated to the new Runtime database.
The old Runtime database is not deleted. Keep the old database until the
IndustrialSQL Server 9.0 historian migration is validated.
There is no migration for the content of the Holding database, because this
database is only used to temporarily hold data when importing an InTouch data
dictionary.

IndustrialSQL Server Historian Installation Guide

52 Chapter 3

Not all of the system tags included in previous versions are included in the 9.0
historian. Any data associated with these obsolete system tags is not migrated.
For the event subsystem, all SQL-based detectors and actions are migrated to
the OLE DB syntax. If you have any custom SQL-based detectors or actions,
you need to rewrite them using the OLE DB syntax.
History data that is stored in SQL Server tables (not history blocks) can be
migrated after the general upgrade has been performed. For example, data
previously contained in the StringHistory table for version 7.1 is migrated to
the new ManualStringHistory table. For more information, see "Migration of
History Data Stored in SQL Server" on page 54.
All of the migration scripts are included on the CD in the following location:
\InSQL\Server\Scripts
The scripts are installed with the historian program files so that you can run
them at any time. The default file path is:
\Program Files\Wonderware\InSQL\Server\Scripts

Upgrading from a Previous Version

Important! Back up your Runtime database before you start the upgrade.

You may be prompted to reboot the computer during the upgrade.

To upgrade from a previous version

1. Back up your Runtime database.
2. If you are upgrading from an IndustrialSQL Server 7.1 historian, upgrade
Microsoft SQL Server 7.0 to Microsoft SQL Server 2000. For more
information, see "Upgrading from Microsoft SQL Server 7.0" on page 56.
3. Uninstall the previous version and keep the Runtime database, the history
blocks, and the log files.
If you try to install the 9.0 historian without first uninstalling the previous
version, you are not allowed to continue with the 9.0 historian installation.

You do not need to uninstall the common components; the 9.0 historian
program installation upgrades them.

IndustrialSQL Server Historian Installation Guide

 Upgrading from a Previous Version 53

4. Install all of the necessary requirements. For more information, see

"Server Requirements" on page 7.
5. Insert the IndustrialSQL Server 9.0 CD into your CD-ROM drive. If the
setup program does not automatically run, double-click Setup.exe in the
root directory of the CD.
6. Follow the prompts to complete the installation of the historian program
files. For more information, see "Installing the IndustrialSQL Server
Historian Program Files" on page 30.
7. If you are installing the historian on the Windows XP Professional SP2 or
Windows 2003 SP1 operating system, the Wonderware OS Configuration
Utility configures certain security options so that the historian runs on
these operating systems. There is no user interface for this utility.
8. Start the Database Configuration Utility.
The utility automatically starts at the end of the historian program file
installation. You can also start the utility at any time by running the
aaHistorianCfg.exe file located in the <installation path>\InSQL\Server
folder.
9. Follow the prompts to start the database configuration.
The number and sequence of dialog boxes that appear are similar to, if not
exactly the same as, the dialog boxes that appear for a new installation.
For information on using this utility, see "Configuring Databases and Data
File Locations" on page 38.
The utility checks for an existing Runtime database. If found, a dialog box
appears, prompting you to confirm the migration of the existing database.
The existing Holding database is deleted.
10. To proceed with the migration, click Yes.
• If a version 7.1 database is found, you are prompted to migrate the
database. The utility renames the existing Runtime database to
Runtime71 and creates the version 9.0 database. If you chose to
migrate, the utility runs the migration scripts (Migrate71To90.sql and
MigrateSQLHistData71to90.sql) to transfer the historian
configuration and history data from the old database.

IndustrialSQL Server Historian Installation Guide

54 Chapter 3

• If a version 8.0.x database is found, you are prompted to migrate the

database. The utility renames the existing Runtime database to
Runtime80 and creates the version 9.0 database. If you chose to
migrate, the utility runs the migration scripts (Migrate80To90.sql and
MigrateSQLHistData80to90.sql) to transfer the historian
configuration and history data from the old database.
At the end of the configuration, the final dialog box appears.

11. Click Finish. You may be prompted to reboot the computer.

12. Click Yes if you want to reboot immediately. You must reboot before
migrating any data from the previous version or using the 9.0 historian.
13. Optionally migrate SQL Server history data. For more information, see
"Migration of History Data Stored in SQL Server" on page 54.

Migration of History Data Stored in SQL Server

The normal SQL Server tables in the Runtime database contain configuration
data and certain types of history data. History data that is stored in the normal
SQL Server tables includes:
• Data in the AnalogManualHistory, DiscreteManualHistory, and
StringHistory tables.
• Event and summary data, which is stored in the EventHistory,
SummaryHistory, SummaryData, AnalogSnapshot, DiscreteSnapshot, and
StringSnapshot tables.
These tables can contain hundreds of thousands of rows, if not millions of
rows. Depending of the amount of data to be migrated, migrating this data can
take a few minutes to many hours, and in some cases, days.

IndustrialSQL Server Historian Installation Guide

 Upgrading from a Previous Version 55

Important! You MUST perform the database migration before the server
goes back into production, because the history table content will be truncated.

Be sure that you have disk space equivalent to two times the size of the
Runtime database on the drive to which the history data will be migrated;
otherwise, the migration may fail. Back up the Runtime database with the
migrated configuration data before migrating the history data.

The scripts used to migrate the SQL Server history data can be found in the
InSQL Server installation directory. By default, this directory is \Program
Files\Wonderware\InSQL\Server\Scripts.
• MigrateSQLHistData71to90.sql
• MigrateSQLHistData80to90.sql
Do not attempt to migrate the data until you complete the upgrade to the
IndustrialSQL Server 9.0 historian. To migrate the data, execute these scripts
using SQL Server Query Analyzer. You may prefer to run the script in blocks
(that is, execute the syntax commands between the GO statements).

Note Data that was stored in the StringHistory table for the IndustrialSQL
Server 7.1 historian is now stored in the ManualStringHistory table.

IndustrialSQL Server Historian Installation Guide

56 Chapter 3

Upgrading from Microsoft SQL Server 7.0

When upgrading Microsoft SQL Server 7.0 to Microsoft SQL Server 2000, the
Installation Selection dialog box will appear. This dialog box will prompt you
to either upgrade the current instance of SQL Server, or to create a new
instance.

Select to upgrade the current instance of Microsoft SQL Server. Select the
Upgrade, remove, or add components to an existing instance of SQL
Server option. Do not create a new instance.
Also, to change from SQL Server only authentication, do either of the
following:
• Configure the Microsoft SQL Server 2000 to use mixed mode
authentication.
• Configure the Microsoft SQL Server 2000 to use Windows authentication.
Then, either manually create corresponding Windows users and groups for
your existing SQL Server users and roles or convert them to Windows
users and groups.

IndustrialSQL Server Historian Installation Guide

 Upgrading from a Previous Version 57

Upgrading the IndustrialSQL Server Historian

to a Different Computer
When you are upgrading a server system such as the IndustrialSQL Server
historian, you may need to deploy the latest version on a different computer. In
this case, you need to build and configure the new computer first, and then
migrate the database and history data files stored in the SQL Server tables (not
the history blocks).

To upgrade to a new computer

1. On the new computer, install any of the supported operating systems. For
more information, see "Server Requirements" on page 7.
2. Install Microsoft SQL Server 2000 Service Pack 3a. Select the same
collation and sort order that was used for your previous SQL Server
installation. For more information, see "Microsoft SQL Server
Installation" on page 28.
3. Move the existing Runtime database (.mdf) and log file (.ldf) to the SQL
Server on the new computer. You could use the SQL Server Copy
Database wizard or you could restore a backup to the new computer.
4. Install the IndustrialSQL Server 9.0 historian program files. For more
information, see "Installing the IndustrialSQL Server Historian Program
Files" on page 30.
5. Run the historian Database Configuration utility to configure the history
data file locations and migrate the existing database to version 9.0. For
more information on this utility, see "Configuring Databases and Data File
Locations" on page 38.
• If a version 7.1 database is found, you are prompted to migrate the
database. The utility renames the existing Runtime database to
Runtime71 and creates the version 9.0 database. If you chose to
migrate, the utility runs the migration scripts (Migrate71To90.sql and
MigrateSQLHistData71to90.sql) to transfer the historian
configuration and history data from the old database.
• If a version 8.0.x database is found, you are prompted to migrate the
database. The utility renames the existing Runtime database to
Runtime80 and creates the version 9.0 database. If you chose to
migrate, the utility runs the migration scripts (Migrate80To90.sql and
MigrateSQLHistData80to90.sql) to transfer the historian
configuration and history data from the old database.
For more information on migrating history data stored in the SQL Server
tables to the new database, see "Migration of History Data Stored in SQL
Server" on page 54.
6. Copy history blocks from the previous version to the new computer.
7. Use the historian System Management Console to update the storage
locations and system parameters to configure paths as per your new
hardware configuration and the Runtime parameters as per your new
implementation.

IndustrialSQL Server Historian Installation Guide

58 Chapter 3

IndustrialSQL Server Historian Installation Guide

 System Sizing Examples 59

A P P E N D I X A

System Sizing Examples

To help you determine how to size your system, performance reports are
provided for different IndustrialSQL Server historian configurations.

Contents
• Server 1: P4 3.2 GHz Single Processor
• Server 2: P4 3.0 GHz Dual Processor
• Server 3: P4 2.7 GHz Xeon Quadruple Processor

Server 1: P4 3.2 GHz Single Processor

IndustrialSQL Server Historian Specifications
• P4 3.2 GHz CPU
• 1 GB RAM
• 512 MB Virtual Memory
• 1 GB NIC
• Windows XP Professional SP2
• Microsoft SQL Server 2000 Standard Edition SP3
• SQL memory clamped @ 512 MB
• 12-hour history block duration
Tag Information
Tag count (total) = 5,187
Analog tags = 2,607
Discrete tags = 2,285
String tags = 295
Manual tags = 17
Update rate of +/- 5,000 updates/second
Remote IDAS
None.
Event Information
• 3 snapshot events, each having:

IndustrialSQL Server Historian Installation Guide

60 Appendix A

• 1 analog snapshot
• 1 discrete snapshot
• 1 string snapshot
• 2 summary events, each having:
• 1 AVG calculation (1 tag every 8 hours)
• 1 MAX calculation (1 tag every 8 hours)
• 1 MIN calculation (1 tag every 8 hours)
• 1 SUM calculation (1 tag every 8 hours)
• 1 SQL insert every 4 hours
• 2 SQL multi-point updates every hour
Query Load
For the following seven queries, each are occurring at different times in the
hour:
• 1 query (trend):
• live mode - 1 second update
• 1-hour duration
• 10 tags (7 analogs, 3 discretes)
• 1 query: 1-hour range / hour (1 tag)
• 4 queries: 15-minute range / hour (1 tag)
• 1 query: 24-hour report every 24 hours (25 to 30 tags)
Performance Results

Category Value
Average CPU load (%) 4.74
IndustrialSQL Server historian memory (Private Bytes) consumption (MB) 138
Number of online history blocks 207
Uncompressed hard drive disk space per history block (MB) 925

Server 2: P4 3.0 GHz Dual Processor

IndustrialSQL Server Historian Specifications
• P4 3.0 GHz Dual CPU
• 2 GB RAM
• 3072 MB Virtual Memory
• 1 GB NIC
• Windows 2003 Standard Server
• Microsoft SQL Server 2000 Standard Edition SP3

IndustrialSQL Server Historian Installation Guide

 System Sizing Examples 61

• SQL memory clamped @ 1024 MB

• 4-hour history block duration
Tag Information
Tag count (total) = 63,000
Analog tags = 39,359
Discrete tags = 19,734
String tags = 295
Manual tags = 5,057
Update rate of +/- 30,000 updates/second
Remote IDAS
One remote IDAS:
• P4 1.7 GHz
• 1 GB RAM
• 34,000 tags via the remote IDAS and the rest via the local IDAS

Note Because this configuration was used for performance and stress testing,
the remote IDAS tag count is more than the recommended 30,000 maximum.

Event Information
• 3 snapshot events, each having:
• 1 analog snapshot
• 1 discrete snapshot
• 1 string snapshot
• 2 summary events, each having:
• 1 AVG calculation (1 tag every 8 hours)
• 1 MAX calculation (1 tag every 8 hours)
• 1 MIN calculation (1 tag every 8 hours)
• 1 SUM calculation (1 tag every 8 hours)
• 1 SQL insert every 4 hours
• 2 SQL multi-point updates every hour
Query Load
For the following seven queries, each are occurring at different times in the
hour:
• 1 query (trend):
• live mode - 1 second update
• 1- hour duration
• 10 tags (7 analogs, 3 discretes)
• 1 query: 1-hour range / hour (1 tag)
• 4 queries: 15-minute range / hour (1 tag)
• 1 query: 24-hour report every 24 hours (25 to 30 tags)

IndustrialSQL Server Historian Installation Guide

62 Appendix A

Performance Results

Category Value
Average CPU load (%) 9.89
IndustrialSQL Server historian memory (Private Bytes) consumption (MB) 680
Number of online history blocks 104
Uncompressed hard drive disk space per history block (GB) 2.47

Server 3: P4 2.7 GHz Xeon Quadruple

Processor
IndustrialSQL Server Historian Specifications
• P4 2.7 GHz Xeon Quad
• 8 GB RAM
• 4096 MB Virtual Memory
• 1 GB NIC
• Windows 2003 Enterprise Server
• Microsoft SQL Server 2000 Standard Edition SP3
• SQL memory clamped @ 3967 MB
• 2-hour history block duration
Tag Information
Tag count (total) = 133,941
Analog tags = 73,600
Discrete tags = 53,560
String tags = 6920
Update rate of +/- 50,000 updates/second
MDAS
In the total tag count, 4009 tags originated from an Industrial Application
Server.
Remote IDAS
Two remote IDASs:
• Remote IDAS 1: P4 1.9 GHz, 1 GB RAM
• Remote IDAS 2: P4 2.5 GHz, 512 MB RAM
44,370 tags via the remote IDAS 1
45,584 tags via the remote IDAS 2
44,383 tags via the local IDAS

Note Because this configuration was used for performance and stress testing,
the remote IDAS tag counts are more than the recommended 30,000
maximum.

IndustrialSQL Server Historian Installation Guide

 System Sizing Examples 63

Event Information
• 3 snapshot events, each having:
• 1 analog snapshot
• 1 discrete snapshot
• 1 string snapshot
• 2 summary events, each having:
• 1 AVG calculation (1 tag every 8 hours)
• 1 MAX calculation (1 tag every 8 hours)
• 1 MIN calculation (1 tag every 8 hours)
• 1 SUM calculation (1 tag every 8 hours)
• 1 SQL insert every 4 hours
• 2 SQL multi-point updates:
• 1 every 15 minutes
• 1 every 30 minutes
Query Load
For the following seven queries, each are occurring at different times in the
hour:
• 1 query (trend):
• live mode - 1 second update
• 15-minute duration
• 15 tags (10 analogs, 5 discretes)
• 1 query: 1-hour range / hour (1 tag)
• 4 queries: 15-minute range / hour (1 tag)
• 1 query: 24-hour report every 24 hours (25 to 30 tags)
Performance Results

Category Value
Average CPU load (%) 13.9
IndustrialSQL Server historian memory (Private Bytes) consumption (MB) 1,478
Number of online history blocks 470
Uncompressed hard drive disk space per history block (average GB) 1.73

IndustrialSQL Server Historian Installation Guide

64 Appendix A

IndustrialSQL Server Historian Installation Guide

 Index 65

Index
A F
acquisition FAT 12
loading 17 fault-tolerant servers 9
ActiveEvent feature lines 21
installing 30
ActiveFactory 26 H
analog tags
disk space requirements 15 hardware recommendations
anti-virus software 26 storage 12
hardware requirements
B disk space 12, 13
IDASs 10
blocks IndustrialSQL Server 7
See history blocks System Management Console 9
history blocks
C disk space requirements 14
licensing 24
client connections 19, 20 history data
cluster licensing 24
licensing 22 migrating from older versions 54
common components 29 Holding database
Configuration Editor 30 disk space 13
Configuration Utility 38 hyperthreading 25
connections 19
CSV data I
licensing 24
IDASs
D installing 29
licensing 23
data acquisition performance 17
See acquisition requirements 10
data blocks security 11
See history blocks InBatch 26
data files InControl 25
See history blocks, Runtime database Industrial Application Server 25
data retrieval IndustrialSQL Server
See retrieval components 29
data storage documentation set 5
installation 28, 30
See storage
installing 27
database
loading 16
configuring 38
memory requirements 15
database files
menu shortcuts 50
disk space requirements 13
modifying installation 44
DDE
repairing 42
Windows Server 2003 8, 18, 25
requirements 7
discrete tags
testing the install 42
disk space requirements 15
uninstalling 47
disk sizing 11
upgrading 51, 52, 57
disk space
InSQL Console
history blocks 14
planning 12 See also Management Console, Configuration
software 13 Editor
document conventions 6 InSQL Database Export/Import Utility
documentation set 5 requirements 9
installation
E about 27
components 27
event data IndustrialSQL Server 27, 28, 30
migrating from older versions 54 Microsoft SQL Server 28
modifying for IndustrialSQL Server 44

IndustrialSQL Server Historian Installation Guide

66 Index

InTouch History Importer 10 repairing

InTouch WindowViewer 25 IndustrialSQL Server 42
InTrack 26 requirements
InSQL Database Export/Import Utility 9
L retrieval
loading 17
LAN 18 Runtime database
license information disk space 13
agreement 32 migration 51
License Viewer 29
licensing S
about 21
feature lines SCSI 12
cluster 22 security
data modification 24 remote IDASs 11
history duration 24 software requirements
operating system 22 IDASs 10
processor 24 IndustrialSQL Server 7
remote IDAS 23 System Management Console 9
tag count 22 SPCPro 26
loading SQL Server
IndustrialSQL Server 16 See Microsoft SQL Server
logon parameters 35 SQL statements
licensing 24
M storage
disk sizing 11
Management Console 30 hardware recommendations 12
memory loading 17
requirements 7, 15 performance 17
Microsoft Client Utilities 28 See also history blocks
Microsoft SQL Server 8 string tags
installation 28 disk space requirements 15
migration SuiteLink 18
See upgrading SuiteVoyager 26
summary data
N migrating from older versions 54
system
named pipes 28 sizing 59
network cards 18 System Management Console
network protocol 21 installing 30
networking 18 requirements 9
NTFS 12, 14

O T
tags
operating systems licensing 22
licensing 22 TCP/IP 18, 28
non-English 25
U
P
uninstalling 47
performance 15 upgrading 51
examples 59 IndustrialSQL Server 52, 57
IDASs 17 Microsoft SQL Server 56
storage 17 user account 35
physical memory 7
process network 18 V
processors
licensing 24 variable length strings 15
protocols 21 virtual memory 7
recommendations 18 virus scanners 26
R W
RAID 12 WAN 18

IndustrialSQL Server Historian Installation Guide

 Index 67

Windows 2000 9, 10, 22

Windows 2000 Advanced Server 8, 9
Windows 2000 Professional 8
Windows 2000 Server 8, 9
Windows 2003 22
Windows Server 2003 8, 9, 10, 18, 25
Windows XP 8, 9, 10

IndustrialSQL Server Historian Installation Guide

68 Index

IndustrialSQL Server Historian Installation Guide