ReadMe

# Wonderware IndustrialSQL Server 9.0 Historian ReadMe

Last revision: 7/21/2005

This document contains important information about the WonderwareŇ IndustrialSQL Server™ 9.0 historian. Please carefully review this document for known issues in this version and changes to the IndustrialSQL Server documentation included on this CD.

System Requirements

Installation Information

Known Issues – IndustrialSQL Server Historian

Known Issues – IndustrialSQL Server Historian Running in a Cluster

Known Issues - IndustrialSQL Server Documentation

Release Summary

IndustrialSQL Server Documentation

# System Requirements

The IndustrialSQL Server 9.0 historian is supported on the following operating systems and versions of Microsoft SQL Server. For detailed system requirements, see the IndustrialSQL Server Historian Installation Guide (InSQLInstall.pdf) or installation Help.

IndustrialSQL Server Historian:

- Windows 2000 Professional SP4, with SQL Server 2000 Personal Edition SP3a
- Windows XP Professional SP2, with SQL Server 2000 Personal Edition SP3a
- Windows 2000 Server SP4, with SQL Server 2000 Standard Edition SP3a
- Windows Server 2003 Standard Edition, with SQL Server 2000 Standard Edition SP3a
- Windows Server 2003 SP1 Standard Edition, with SQL Server 2000 Standard Edition SP3a

- Windows Server 2003 Enterprise Edition, with SQL Server 2000 Enterprise Edition SP3a

- Windows Server 2003 SP1 Enterprise Edition, with SQL Server 2000 Enterprise Edition SP3a

IndustrialSQL Server Configuration Tools:

- Windows XP Professional SP2
- Windows 2000 Professional SP4
- Windows 2000 Server SP4
- Windows Server 2003 Standard Edition

- Windows Server 2003 SP1 Standard Edition

Remote IDAS:

- Windows XP Professional SP2
- Windows 2000 Professional SP4
- Windows 2000 Server SP4
- Windows Server 2003 Standard Edition

- Windows Server 2003 SP1

< top of document >

# Installation Information

The InSQLInstall.pdf file, located on the IndustrialSQL Server CD in the \UserDocs\English directory, includes comprehensive information on system requirements and recommendations, installation, upgrades and migration, and system sizing examples. If you are installing the IndustrialSQL Server historian or upgrading from a prior version, read this information prior to starting the installation or upgrade.

The CD-key for installing Microsoft SQL Server is: GJDD4-GMYXW-GQR4C-KT4P9-QDQGB

The InSQLEnterprise.pdf file, located on the IndustrialSQL Server CD in the \UserDocs\English directory, is a deployment guide that includes specific instructions about implementing the IndustrialSQL Server historian in a clustered environment.

The Microsoft SQL Server Enterprise Edition CD includes an embedded CD key. You will not be required to provide a CD key in order to install Microsoft SQL Server Enterprise Edition.

< top of document >

# Known Issues – IndustrialSQL Server Historian

### Anti-Virus Software Issues

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 folder, be sure that you configure the anti-virus software accordingly.

### L00011101: When tags with the access name 'Galaxy' are imported into the IndustrialSQL Server historian, an I/O Server named "\NA\NA" is created, with a topic named "NA."

Workaround: The 'Galaxy' access name is from Industrial Application Server tag definitions. InTouch applications that use Industrial Application Server should not be imported into the IndustrialSQL Server historian directly from the Tagname.x file. Use the Configuration Export and Import Utility to remove the Galaxy items and then import the remaining tags into the IndustrialSQL Server historian.

### L00011169: Inconsistent date formats between the OPENQUERY function and four-part queries on non-English language systems.

For the OPENQUERY function, YYYY/MM/DD and YYYY-MM-DD are acceptable. However, for a four-part query, YYYY/DD/MM and YYYY-DD-MM are required. The four-part format doesn't work in the OPENQUERY function and the OPENQUERY function format doesn't work in a four-part query. The default German formats of DD.MM.YY and DD.MM.YYYY works in both the OPENQUERY function and four-part queries.

### L00012260: SELECT INTO combined with ORDER BY fails.

With Microsoft SQL Server 2000 SP3, if you use a SELECT...INTO statement from an IndustrialSQL Server extension table (e.g. AnalogHistory) that includes an ORDER BY clause into a SQL Server table, the statement will fail; without an ORDER BY, it will succeed. The workaround is to not use the ORDER BY on the SELECT...INTO statement, but to instead place it on queries against the new table created by the SELECT…INTO statement. For example, do not use:

"SELECT * INTO MyTable FROM AnalogHistory ORDER BY DateTime"

and then:

"SELECT * FROM MyTable"

Instead, use:

"SELECT * INTO MyTable FROM AnalogHistory"

and then:

"SELECT * FROM MyTable ORDER BY DateTime"

### L00014736: String tags are truncated to 511 characters for REALTIME and ORIGINAL inserts

If you are inserting original or real-time data for string tags, the maximum length of the string value is 511 characters. If the string value is 512 characters, the 512th character will be discarded. The IndustrialSQL Server historian will correctly store the full 512 characters if the string value is acquired from an I/O Server via IDAS or inserted as "latest."

### L00014755: Importing long string tag values from a CSV file.

When importing string data from a CSV file, you cannot combine strings longer than 256 characters into single line of the CSV. You must instead place them on separate lines. The data is correctly inserted for a single value per line, even when the string is longer than 256 characters.

### L00021328: For the InSQL I/O Server (InSQLIOS), the item name is not case-sensitive.

If two tags have the exact same name but differ in case, the values for the tag that occurs first in the active image will be passed to InSQL I/O Server clients.

### L00021564: For single point updates via a CSV file, if the CSV file contains more than one value with the same ending timestamp for the same tag, the updates are not terminated (NULL value) until the next block change-over.

Workaround: Make sure that multiple updates in single CSV file do not have the same end time.

### L00023669: If the IndustrialSQL Server historian is running on the Windows Server 2003 operating system without Service Pack 1, the remote IDAS goes into store-and-forward mode at regular intervals, even though the connection to the historian is still valid.

The IndustrialSQL Server historian running on Windows Server 2003 requires more processor time than the same configuration running under Windows 2000 Server, due to differences in the operating systems. For data storage tasks, expect Windows Server 2003 to require a processor approximately three times faster than a comparable system running Windows 2000 Server. While, in general, the IndustrialSQL Server historian quite effectively uses multiple processors, this particular limitation cannot be addressed with additional processors. For example, the dual 933MHz processor described in the system sizing examples is adequate for a 25,000-tag IndustrialSQL Server system running on Windows 2000 Server. Upgrading the system to Windows Server 2003 would require replacing the system with approximately a dual 2.7 GHz system rather than upgrading it to a quad 933MHz. These performance differences also applied to the IndustrialSQL Server 8.0 SP2 historian, which was the first release to support Windows Server 2003.

IDAS goes into store-and-forward mode because the storage subsystem does not process data sent by IDAS in timely fashion. In all cases, store-and-forward functions correctly, and data will not be lost.

Workaround: install Windows Server 2003 SP1.

### L00028021: If you use the Database Configuration Export and Import utility to import tag definitions with Japanese characters in the tag description, the error "Engineering unit does not exist" occurs.

Workaround: Convert the exported text file to SJIS, one of the Japanese character codes, before importing the file.

### L00034386: If dynamic reconfiguration occurs for a tag receiving late data, and a new history block is required, the late data is not available for retrieval from disk until the time span by which the data was late has expired.

For example, if the data is late by ten minutes, then data will be unavailable for that tag for ten minutes.

### L00034465: If you have upgraded to the IndustrialSQL Server 9.0 historian from a previous version, you must change the SuiteLink client application name for the IndustrialSQL Server historian I/O Server from "InSQLIOS" to "aahIOSvrSvc."

### L00037017: If the IndustrialSQL Server historian installation does not require a computer restart, a "Stack overflow" exception in wwPerf.dll error occurs when the InSQLIOS service is started.

Workaround: Restart the computer after installing the historian, even if not prompted to do so.

### L00037116: If the IndustrialSQL Server historian installation does not require a computer restart, IDASs fail to communicate to all local and remote I/O Servers because the Suitelink.dll could not be loaded.

Workaround: Restart the computer after installing the historian, even if not prompted to do so.

### L00037200: The message "Failed to retrieve product name and/or version resources" is logged by the IndustrialSQL Server historian I/O Server, InSQLIOS (aahIOSvrSvc), during startup.

This message can be ignored.

### L00037894: After installing a valid license file, if you attempt to insert manual data using a SQL statement, Microsoft SQL Server returns an error.

Workaround: After installing a valid license file, completely shut down the historian using the Shutdown (and disable) InSQL command and then restart the historian using the Enable (allow to run) InSQL command. You could also restart the computer. If a running historian cannot be interrupted, you can alternatively use a CSV file to insert the data until it is appropriate to take the historian offline.

### L00039362: For "fast load" imports, the "swinging door" storage algorithm is not applied.

### L00039808 Warning message regarding snapshot write operation taking longer than 10 seconds needs to be more accurately informative.

This message means the data throughput rate of the system is exceeding the disk I/O write capabilities. If this situation persists, there is the possibility of data corruption and data loss.

This problem can occur on high throughput systems (updates/sec) and/or during extensive (circular path) disk activity generated by file copy operations, for example.

To solve this problem, reduce the data throughput (using deadbands, for example) and/or to upgrade your hardware for optimal disk access.

< top of document >

# Known Issues - IndustrialSQL Server Historian Running in a Cluster

### L00019269: In some circumstances, when a cluster failover occurs due to a network failure on the active cluster node, NULLs will not be stored for system tags and I/O tags if the tag data is being acquired by a local IDAS.

The resulting behavior is that after the system has failed over, there is a "flat line" during the failover time, rather than a gap. This expected behavior does not occur for remote IDAS data.

### L00019335: In some circumstances, if you shut down the IndustrialSQL Server historian on the active cluster node, a data loss of up to 30 seconds may occur before the store-and-forward functionality starts up on the remote IDAS.

It is recommended that you move the cluster resources to the failover node prior to shutting down the IndustrialSQL Server historian.

### L00019356: In some circumstances, when a failover is initiated just after the reconnection of a remote IDAS (from a previous network failure, for example), the system may take up to five minutes to complete the failover.

This does not affect the data collected by the remote IDAS, as this data will be stored and forwarded as soon as the failover is complete.

### L00037750: Uninstalling IndustrialSQL Server from a cluster does not remove historian resources and a resource type created during installation.

Workaround: Run the following commands from a command prompt:

REM delete Historian resource:

cluster resource "IndustrialSQL Server" /delete

REM delete Historian resource type:

cluster restype Historian /delete /type

REM take network name resource offline [name varies]

cluster resource "Historian Network Name (<Virtual InSQL server name here>)" /off

REM delete network name resource [name varies]

cluster resource "Historian Network Name (<Virtual InSQL server name here>)" /delete

REM take IP address resource offline [name varies]

cluster resource "Historian IP Address 1 (<Virtual InSQL server name here>)" /off

REM delete IP address resource [name varies]

cluster resource "Historian IP Address 1 (<Virtual InSQL server name here>)" /delete

REM take IP address resource offline [name varies]

cluster resource "Historian IP Address 2 (<Virtual InSQL server name here>)" /off

REM delete IP address resource [name varies]

cluster resource "Historian IP Address 2 (<Virtual InSQL server name here>)" /delete

< top of document >

# Known Issues – IndustrialSQL Server Documentation

The following table describes corrections to the documentation.

### Item

### Location of Change

### Existing Documentation

### Change

1 | InSQLConcepts.pdf: "Swinging Door Deadband: Rate, Value, and Deadband Override Period" section, page 78 InSQLBooks.chm: "Swinging Door Deadband: Rate, Value, and Deadband Override Period" topic | "To allow for better representation, a deadband override period may optionally be specified. If the elapsed time since the last stored point exceeds the deadband override period, the last received point before the time at which the deadband override period expired is stored, regardless of value and rate deadband. In this example, it would be point 9. The data actually stored to disk (points 1, 2, 9, and 15) is a better approximation of the original data." | "To allow for better representation, a deadband override period may optionally be specified. If the elapsed time between the last stored point and the currently received point is more than the specified deadband, then the point immediately prior to the currently received point is stored. In this example, the elapsed time between point 2 and point 10 is more than the deadband, so point 9 is stored. The data actually stored to disk (points 1, 2, 9, and 15) is a better approximation of the original data."
2 | InSQLAdmin.pdf: "Formatting the CSV File for a Normal Import" section, page 144 InSQLBooks.chm: "Formatting the CSV File for a Normal Import" topic | -- | Add the following paragraph: "For a fast load CSV import, the end time of the current block in the block80.inf file is considered to be the current time, not the current system timestamp. The end time in the .inf file is updated by the storage subsystem every 20 seconds."
3 | InSQLConcepts.pdf: "Modification Tracking for Historical Data Changes" section, page 38 InSQLBooks.chm: "Modification Tracking for Historical Data Changes" topic | "The count of the number of consecutive data value changes per tag is stored in the NewValue column of the ModLogColumn table." | "The total count of consecutive value changes attempted per tag is stored in the NewValue column of the ModLogColumn table."
4 | InSQLAdmin.pdf: "Importing Data from an InTouch History File" section, page 135 InSQLBooks.chm: "Importing Data from an InTouch History File" topic | -- | Add the following bullet item: "If you have a large amount of data to import, process the data in batches, starting from the most recent data to the oldest data. For example, you want to import one year's worth of InTouch history. Divide up the data so that one month of data is included in a batch. When you import the most recent batch, the utility automatically starts with the most recent block and then proceeds backwards. Then, import the second-most recent batch, and so on."
5 | InSQLConcepts.pdf: "IDAS Late Data Handling" section, page 60 InSQLBooks.chm: "IDAS Late Data Handling" topic | -- | Add the following bullet item under the data throughput rules: "Late data must not encompass more than six history blocks at any given point of time."

< top of document >

# Release Summary

New features for the IndustrialSQL Server 9.0 historian include:

· Better integration with Industrial Application Server.

· You can browse for and query data based on the Industrial Application Server model view when using a client tool such as ActiveFactory Trend.

· Improved data acquisition.

· The historian supports the acquisition of late data via IDAS, at data rates up to 30% of the sustainable real-time data rate on a given hardware configuration.

· You can configure an IDAS to start acquiring and locally caching data if the historian is not available when IDAS starts. This is called autonomous startup.

· Additional functionality for data storage and retrieval.

· You can specify, at topic level, that data is to be timestamped at the server (that is, overwrite the source timestamp).

· You can specify the translation between OPC quality and IndustrialSQL Server-specific quality, quality detail and NULL values, to better support client-side data presentation.

· Additional column(s) in the History tables and related tables expose a textual description of basic OPC quality values.

· The historian supports additional modes of retrieving historized data, including best-fit, time-weighted average, minimum, maximum, integral, slope, counter, and time-in-state. Also, linear interpolation of results based on cyclic retrieval of analog tags has been added. Interpolation can be either tag-specific or query-specific. You can also control the timestamping of aggregate results and how quality should be interpreted and displayed for those aggregates.

· More storage filtering options.

· "Rate deadband" filtering (or "swinging door" filtering algorithm) has been added for data storage.

· Data storage does not require a filtering algorithm, so that all data values that are received from data sources can be stored ("forced" storage).

· Improved support for SQL Server security.

· Windows integrated security is supported, as well as SQL Server mixed-mode security.

· High-availability support.

· Built-in support is provided for Stratus ft3500 fault-tolerant servers and for Microsoft dual-node, active/passive failover clusters.

· Reduced memory consumption and additional diagnostics.

· An indexing subsystem runs as its own service and selectively loads and unloads history block data based on user requests for data, rather than caching the entire set of history blocks in memory.

· System tags have been added to provide better diagnostic capabilities for SCADA-type environments.

< top of document >

# IndustrialSQL Server Documentation

The IndustrialSQL Server 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 provides information specific to installing IndustrialSQL Server on a Windows cluster. It also includes information about configuring the cluster itself (independent of IndustrialSQL Server). This is the only document that addresses functionality and differences unique to using the IndustrialSQL Server historian on a cluster.

- 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 installation CD. You can easily print information from the PDF files. The IndustrialSQL Server documentation is also provided as an online Help file, which can be accessed from the System Management Console management tool. An installation Help file is also available from within the installation program.

Note: Any information contained in the FactorySuite System Administrator's Guide regarding IndustrialSQL Server is superseded by the documents referenced above.

< top of document >

### © 2005 Invensys Systems, Inc. All Rights Reserved.