Rockwell Automation FactoryTalk View Site Edition Users Guide - Manual (Page 585)

22 • S ETTING UP DATA LOGGING
22–7
•
•
•
• •
22
•
Pla
ceho
lde
r
Selecting the ODBC database format
When you select ODBC database as the storage format, type the path and file name of the
ODBC data source, and specify the ODBC tables that will be used, or create new tables.
To create tables for a new data source, click Create Tables. If FactoryTalk View cannot
create the tables automatically, you will have to open the database using its editing tool,
and create the tables manually.
To extend the length of the message to 1999 for a Microsoft SQL Server or Oracle
database, click Extend table. The default length of the message is 254. You can only
extend the table when the length is between 254 and 1999.
To log a longer diagnostic messages to the database, select the Use long message text
check box. The message can be up to 1999 characters. If the check box is not selected, the
message can be no more than 254 characters.
To select an existing table from the specified database, click the Browse button, and then
select a table in the Select ODBC Table dialog box. To view the order, type, length, and
precision of the fields in the table, click the table to select it and then click Details.
For more information, see “Logging data to an existing ODBC data source” on page 22-9.
Setting up log paths
In the Data Log Models editor, use the Paths tab to set up logging paths.
If the storage format is file sets, specify the primary path, and an optional secondary file
path in case the primary path becomes unavailable. If the storage format is ODBC, you
can specify a backup file path for the ODBC database.
Setting up a secondary or backup logging path prevents loss of data. For example, if the
disk space for the primary path becomes full, data logging will switch to the secondary
path, if available, until space becomes available on the primary path. For more
information, see “Switching log paths at run time” on page 22-11.
If you do not set up a secondary path, when the primary path runs out of disk space, data
logging stops and no more log files are created.
For details about options in the Paths tab, click Help.
Make sure the table is successfully extended before you choose to log long messages.
Otherwise the message longer than 254 and all subsequent messages cannot be logged until
the length is extended.