The configuration file is an operating system ASCII file that you can edit with any text editor that can save files in ASCII format. The syntax for each parameter is:
parameter_name={value | DEFAULT}
where:
parameter_name – is the name of the parameter you want to specify
value – is the numeric value for set parameter_name
“DEFAULT” – specifies that you want to use the default value for parameter_name
Example 1 The following example specifies that the transaction can retry to acquire a lock one time when deadlocking occurs during an index page split or shrink:
cpu accounting flush interval=DEFAULT
Example 2 The following example specifies that the default value for the parameter cpu accounting flush interval should be used:
deadlock retries = 1
When you edit a configuration file, your edits are not validated until you check the file using the verify option, read the file with the read option, or restart Adaptive Server with that configuration file.
If all your configuration files are lost or corrupted, you can re-create one from a running server by using the restore subcommand and specifying a name for the new file. The parameters in the new file will be set to the values with which your server is currently running.
Configuration files are nonencrypted ASCII text files. By default, they are created with read and write permissions set for the file owner and read permission set for all other users. If you created the configuration file at the operating system level, you are the file owner; if you created the configuration file from Adaptive Server, using the write or restore parameter, the file owner is the user who started Adaptive Server. Usually, this is the user “sybase.” To restrict access to configuration files, use your operating system’s file permission command to set read, write, and execute permissions as appropriate.
You need to set permissions accordingly on each configuration
file created.
Configuration files are not automatically backed up when you back up the master database. They are operating system files, and you should back them up in the same way you back up your other operating system files.
The output from sp_configure truncates the name of the configuration file due to space limitations. To see the full name of the configuration file, use:
select s1.value2 from syscurconfigs s1, sysconfigures s2 where s1.config = s2.config and s2.name = "configuration file"
