ODBC Database Destination Setup settings
Use the following settings in
ODBC Database Destination Setup
to set up how FactoryTalk Diagnostics
sends messages to an ODBC data source. To send messages from multiple computers, configure the destination on each computer where the FactoryTalk Diagnostics
service is installed.Message Buffering
Setting | Description |
|---|---|
Log message to database every: | Type a number and select a unit of time (seconds, minutes, hours, or days) to specify how frequently to send messages to the database. The numeric range is from 1 through 999. The default is every 2 minutes. FactoryTalk Diagnostics buffers messages locally on each computer where the FactoryTalk Diagnostics service is installed. At the specified interval, these messages are sent to the ODBC-compliant database.To maintain data integrity, ensure that messages are sent to the database before the local log becomes full, or before events in the local log are overwritten. |
Buffer message locally for up to: | If messages cannot be sent to the database, the messages are buffered locally. Type a number and select a unit of time (hours or days) to specify the size of the local buffer. The numeric range is from 1 through 999. The default is 12 hours. The buffer size must be larger than the frequency at which messages are sent to the database. |
ODBC Data Source
Setting | Description |
|---|---|
Data source name: | To select an existing data source, type the path and file name of a system or file ODBC data source, or select Browse (...) to open Select Data Source.
To create a new data source, select New . Follow the instructions in the Create New Data Source wizard to create the new data source. |
Target Table: | Specify the name of the table within the ODBC data source to which to send messages, or create a new table.
To extend the length of the message to 1999 characters for a SQL Server or Oracle database, select Extend table . Extending a table for a Access database is not supported. The default length of the message is 254 characters. Extending the table is only permitted when the message length is between 254 and 1999 characters.To log long diagnostic messages to the database, select the box next to Use long message next . The message can be up to 1999 characters. If the check box is not selected, the message can be no more than 254 characters. Make sure the table is successfully extended before you choose to log long messages. Otherwise the message longer than 254 characters and all subsequent messages cannot be logged until the length is extended. |
Maintain connection | Specify whether to maintain the connection to the ODBC database for a particular length of time or indefinitely. To maintain it for a certain length of time, enter the number of minutes. |
Login required | Select this check if the database is secured and the user needs to log in. When using Windows authentication with a SQL Server database, select this check box. |
Database user ID | If login is required for this ODBC database, type the login user ID. If your database does not support a user ID, enter a space in this box. When using Windows authentication (rather than SQL Server authentication), enter the fully-qualified user name in the format DOMAIN\UserName or user@domain.com (for UPN-style entries). If a fully-qualified user name is not used, the connection to the database might fail. |
Password | If login is required, type the login password. When using Windows authentication with a SQL Server database, ensure that the password matches the Windows authentication password for the user. |
Confirm password | Retype the password to confirm it. |
Provide Feedback