Last revision: 5/19/2005
This document contains important information about the WonderwareŇ IndustrialSQL Server™ 8.0 with SP3a historian. Please carefully review this document for known issues in this version and changes to the IndustrialSQL Server documentation included on this CD.
Known Issues – IndustrialSQL Server
Known Issues - IndustrialSQL Server Documentation
IndustrialSQL Server Documentation
Note: This release does not support upgrades from IndustrialSQL Server 8.0 Enterprise Edition.
Software components and database entities used by versions of ActiveFactory software earlier than 9.0 have been removed.
The IndustrialSQL Server 8.0 SP3a historian is supported on the following operating systems.
IndustrialSQL Server:
InSQL Console client tool:
Remote IDAS:
The InSQLInstall.pdf file, located on the IndustrialSQL Server CD in the \UserDocs 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 SQLServer_Install.doc, located on the IndustrialSQL Server CD in the root directory, describes how to correctly install Microsoft SQL Server 2000 for use with the IndustrialSQL Server historian. You can open this file in WordPad. This file contains screen shots of the appropriate selections for dialog boxes presented during the SQL Server 2000 installation/upgrade for easy reference. This information is also included in the InSQLInstall.pdf.
The CD-key for installing Microsoft SQL Server is: GJDD4-GMYXW-GQR4C-KT4P9-QDQGB
You must upgrade to ActiveFactory 9.0 or later software.
Workaround: Check all custom logins and set the default database to the Runtime database using SQL Server Enterprise Manager.
This issue affects I/O Server failover, where the I/O Server is running on the Windows 98 operating system. The I/O Server failover from a Windows 98 computer to Windows 2000 computer works, but the failback from Windows 2000 to Windows 98 does not occur.
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.
Do not create tags with an acquisition type of "Not Acquired." This will be prohibited in the user interface in future releases.
Workaround: For systems with very large tag counts (50,000 tags or more), if you modify all or nearly all tags in the system (such as changing the I/O topics for the bulk of the items) stop and restart the system to implement these changes, instead of using dynamic reconfiguration. Starting and stopping the system will implement the changes faster.
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.
Workaround: When adding tags, do not attempt to insert/import data for the new tags while the system is in the process of executing a history block changeover. Either complete the data insert/import prior to requesting a history block changeover or wait until the history block changeover is complete before inserting/importing the data. The latter is the preferred solution.
Workaround: Do not modify the "Samples In Active Image" value for variable length string tags. By design, the system should not permit modification of this parameter, and the user interface will be modified in a future release to prohibit this.
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"
If you change the type of a string tag from variable length to fixed length, history data will not be stored for the tag until the IndustrialSQL Server historian is restarted. If you change the type from fixed length to variable length, data storage works properly.
Installation of the IndustrialSQL Server historian on a computer without a parallel port produces the following error: "The Sentinel service depends on the Parport service which failed to start..." The licensing system continues to work correctly when using a "soft" license, but hardware keys are not supported. Disabling the "Wonderware License Manager" service will inhibit the error message without impacting "soft" license management.
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
When importing string data from a .
In Windows Server 2003, specifying a remote storage location by mapping a drive is not allowed. The workaround is to specify the remote storage location by its UNC name. For example, instead of specifying it as "H:\Alternate", where H: is a mapped drive, it should be specified as "\\remotemachine\Alternate".
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.
To work around this, make sure that multiple updates in single .csv file do not have the same end time.
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.
The first block contains information that is used by the IndustrialSQL Server historian to retrieve store-and-forward data. Even if some history blocks were forwarded to the historian, data will not be returned from them if the start time is in the missing first block.
A temporary fix has been implemented for this release. If the store-and-forward deletion threshold is reached, the initial block will not be deleted. The forwarded data may have a "gap" between the retained first block and subsequent blocks, if more than one block was deleted to free up space in the store-and-forward directory. Both a cyclic query that retrieves data from the store-and-forward period and a delta query starting in the gap time period will return NULLs for the gap time period. However, a delta query starting prior to the gap time period will return flat-line data for the gap.
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 following historian folders. (These are the default installation folders.)
C:\Program Files\Wonderware\InSQL\Server\InSQL_Log
C:\InSQL
If, during IndustrialSQL Server installation, you choose different folders for the program files and data files, be sure that you configure the anti-virus software accordingly.
The following information should be included in the IndustrialSQL Server Installation Guide and the IndustrialSQL Server Help.
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 following IndustrialSQL Server folders. (These are the default installation folders.)
C:\Program Files\Wonderware\InSQL\Server\InSQL_Log
C:\InSQL
If, during IndustrialSQL Server installation, you choose different folders for the program files and data files, be sure that you configure the anti-virus software accordingly.
The IndustrialSQL Server documentation set includes the following guides:
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 InSQL Console management tool.
Note: Any information contained in the FactorySuite System Administrator's Guide regarding IndustrialSQL Server is superceded by the documents referenced above.