Modifying the Startup Options
When SQL support is enabled in the SCU, the SQL task is automatically added to the FIX SCU Task Configuration dialog box. The SQL task can be customized for your application by adding command parameters.
For example, if you want to define a login delay of five minutes (300 seconds), a maximum SQL command length of 1000 and a command cache of 10, enter the following parameters in each SQL task's Parameters field:
/LD300 /CL1000 /CA10
The following table describes the command parameters available to this task.
|
Parameter |
Description |
Valid Entries |
|
/LDn |
Defines how often the task attempts to log onto the server after it has lost a connection. This parameter is optional. The system defaults to 300 seconds if this parameter is not defined. |
60 seconds (minimum). No maximum limit set. However, most applications do not need more than one hour (3600 seconds). |
|
/CAn |
Stores the specified number of SQL commands in memory (caches) to increase performance. This parameter is optional. Performance benefits vary depending on your relational database. Refer to the Using Command Caching section for more information on using caching. |
User specified. No maximum limit set. However, most applications do not need more than 10 to 100. |
|
/CLn |
Increases the maximum allowable SQL command length from the default of 255. For example, entering /CL1000 allows a command length of 1,000 characters. NOTE: Make sure that the relational database field can handle the number of characters you define for this parameter. |
User specified. |
|
/LM |
Includes ODBC driver information along with relational database error messages. When using this parameter, keep in mind that driver information can be lengthy, and there may not be enough space for the actual error message in enabled alarm destinations. This parameter is optional and if omitted, no driver information is included. |
None required. |
|
/Dn |
Defines a startup delay before attempting to log into the SQL database. Use this parameter if you encounter problems connecting to the database during startup. |
0 to 65535 seconds. |
