YES, NO

When set to YES, the database server automatically adjusts its multiprogramming level, which controls the maximum number of tasks that can be active at a time. If you choose to control the multiprogramming level manually by setting this option to NO, you can still set the initial, minimum, and maximum values for the multiprogramming level.

See -gna database server option and Database server configuration of the multiprogramming level.

When set to YES, statistics for automatic multiprogramming level adjustments appear in the database server message log.

See -gns database server option and Propriété de serveur AutoMultiProgrammingLevelStatistics.

When set to YES, display cache information in the database server messages window whenever the cache size changes.

See -cs database server option and Propriété de serveur CacheSizingStatistics.

When set to YES, the database server collects Performance Monitor statistics.

See -k database server optionand Propriété de serveur CollectStatistics.

When set to YES, no other connections are allowed to any databases on the database server.

See Propriété de serveur ConnsDisabled.

When set to YES, no other connections are allowed to the current database.

The name of the file used to record database server message log information. Specifying an empty string stops logging to the file. Double any backslash characters in the path because this value is a SQL string.

See -o database server option and Propriété de serveur ConsoleLogFile.

The maximum size, in bytes, of the file used to record database server message log information. When the database server message log file reaches the size specified by either this property or the -on server option, the file is renamed with the extension .old appended (replacing an existing file with the same name if one exists). The database server message log file is then restarted.

See -on database server option and Propriété de serveur ConsoleLogMaxSize.

Sets the multiprogramming level of the database server.

See -gn database server option and Database server configuration of the multiprogramming level.

Do not change the setting of this option except on the recommendation of Technical Support.

See Propriété de base de données DatabaseCleaner.

Controls deadlock logging. The value deadlock_logging is also supported. Deadlock logging options can also be configured in the Database Properties window in Sybase Central. The following values are supported:

Once deadlock logging is enabled, you can use the sa_report_deadlocks system procedure to retrieve deadlock information from the database.

See log_deadlocks option.

Displays diagnostic messages and other messages for troubleshooting purposes. The messages appear in the database server messages window.

See -z database server option and Propriété de serveur DebuggingInformation.

Sets the default disk sandbox settings for all databases started on the database server that do not have explicit disk sandbox settings. Changing the disk sandbox settings by using the sa_server_option system procedure does not affect databases already running on the database server. To use the sa_server_option system procedure to change disk sandbox settings, you must provide the secure feature key for the manage_disk_sandbox secure feature.

See -sbx database server option.

Allows automatic statistics management to drop statistics that return bad estimates from the database.

Allows automatic statistics management to drop statistics that have not been used for 90 consecutive days from the database.

Disconnects TCP/IP connections that have not submitted a request for the specified number of minutes. This prevents inactive connections from holding locks indefinitely.

See -ti database server option and Propriété de serveur IdleTimeout.

Sets the time to check for new IP addresses in seconds. The minimum value is 10 and the default is 0. For portable devices, the default value is 120 seconds.

See -xm database server option and Propriété de serveur IPAddressMonitorPeriod.

A liveness packet is sent periodically across a client/server TCP/IP network to confirm that a connection is intact. If the network server runs for a LivenessTimeout period without detecting a liveness packet, the communication is severed.

See -tl database server option and Propriété de serveur LivenessTimeout.

Sets the maximum database server multiprogramming level.

See -gnh database server option and Database server configuration of the multiprogramming level.

Sets the minimum number of messages of each severity and category that can be retrieved using the sa_server_messages system procedure.

See Propriété de serveur MessageCategoryLimit.

Sets the minimum database server multiprogramming level.

See -gnl database server option and Database server configuration of the multiprogramming level.

Specifies the action that the database server takes when an attempt is made to set an option in the list. The supported values are MESSAGE and ERROR. When OptionWatchAction is set to MESSAGE, and an option specified by OptionWatchList is set, a message appears in the database server messages window indicating that the option being set is on the options watch list.

When OptionWatchAction is set to ERROR, an error is returned indicating that the option cannot be set because it is on the options watch list.

You can view the current setting for this property by executing the following query:

SELECT DB_PROPERTY( 'OptionWatchAction' );

See Monitoring option settings and Propriété de base de données OptionWatchList.

Specifies a comma-separated list of database options that you want to be notified about, or have the database server return an error for, when they are set. The string length is limited to 128 bytes. By default, it is an empty string. For example, the following command adds the automatic_timestamp, float_as_double, and tsql_hex_constant option to the list of options being watched:

CALL sa_server_option( 'OptionWatchList','automatic_timestamp,
float_as_double,tsql_hex_constant' );

You can view the current setting for this property by executing the following query:

SELECT DB_PROPERTY( 'OptionWatchList' );

See Monitoring option settings and Propriété de base de données OptionWatchAction.

See Propriété de base de données ProcedureProfiling.

Instructs the database server to capture profiling information for a specific connection ID, without preventing other connections from using the database. When connection filtering is enabled, the value returned for SELECT PROPERTY( 'ProfileFilterConn' ) is the connection ID of the connection being monitored. If no ID has been specified, or if connection filtering is disabled, the value returned is -1.

See Propriété de serveur ProfileFilterConn.

Instructs the database server which logical processors to use on Windows or Linux. Specify a comma-delimited list of processor numbers and/or ranges. If the lower endpoint of a range is omitted, then it is assumed to be zero. If the upper endpoint of a range is omitted, then it is assumed to be the highest CPU known to the operating system. The in_use column returned by the sa_cpu_topology system procedure contains the current processor affinity of the database server, and the in_use column indicates whether the database server is using a processor. Alternatively, you can query the value of the ProcessorAffinity database server property.

The database server might not use all of the specified logical processors in the following cases:

If you specify an invalid processor ID, sa_server_option returns an error.

See -gta database server option and sa_cpu_topology system procedure.

Instructs the database server to capture profiling information for a specific user ID.

See Propriété de serveur ProfileFilterUser.

Instructs the database server to shut down at the specified time.

See -tq database server option and Propriété de serveur QuittingTime.

Instructs the database server to capture the long text plan of the last query executed on the connection. This setting is also controlled by the -zp server option.

When RememberLastPlan is turned on, obtain the textual representation of the plan of the last query executed on the connection by querying the value of the LastPlanText connection property:

SELECT CONNECTION_PROPERTY( 'LastPlanText' );

See -zp database server option and Propriété de serveur RememberLastPlan.

Instructs the database server to capture the most recently prepared SQL statement for each database running on the server. For stored procedure calls, only the outermost procedure call appears, not the statements within the procedure.

When RememberLastStatement is turned on, you can obtain the current value of the LastStatement for a connection by querying the value of the LastStatement connection property:

SELECT CONNECTION_PROPERTY( 'LastStatement' );

When client statement caching is enabled, and a cached statement is reused, this property returns an empty string.

When RememberLastStatement is turned on, the following statement returns the most recently-prepared statement for the specified connection:

SELECT CONNECTION_PROPERTY( 'LastStatement', connection-id );

The sa_conn_activity system procedure returns this same information for all connections.

See -zl database server option and Propriété de serveur RememberLastStatement.

Filter the request logging information so that only information for a particular connection is logged. This filtering can reduce the size of the request log file when monitoring a database server with many active connections or multiple databases. You can obtain the connection ID by executing the following:

CALL sa_conn_info( );

To log a specific connection once you have obtained the connection ID, execute the following statement:

CALL sa_server_option( 'RequestFilterConn', connection-id );

Filtering remains in effect until it is explicitly reset, or until the database server is shut down. To reset filtering, use the following statement:

CALL sa_server_option( 'RequestFilterConn', -1 );

See Propriété de serveur RequestFilterConn.

Filter the request logging information so that only information for a particular database is logged. This can help reduce the size of the request log file when monitoring a server with multiple databases. You can obtain the database ID by executing the following statement when you are connected to the desired database:

SELECT CONNECTION_PROPERTY( 'DBNumber' );

To log only information for a particular database, execute the following statement:

CALL sa_server_option( 'RequestFilterDB', database-id );

Filtering remains in effect until it is explicitly reset, or until the database server is shut down. To reset filtering, use the following statement:

CALL sa_server_option( 'RequestFilterDB', -1 );

See Propriété de serveur RequestFilterDB.

The name of the file used to record request information. Specifying an empty string stops logging to the request log file. If request logging is enabled, but the request log file was not specified or has been set to an empty string, the server logs requests to the database server messages window. Double any backslash characters in the path because this value is a SQL string.

When client statement caching is enabled, set the max_client_statements_cached option to 0 to disable client statement caching while the request log is captured, if the log will be analyzed using the tracetime.pl Perl script.

See -zo database server option and Propriété de serveur RequestLogFile.

This call turns on logging of individual SQL statements sent to the database server for use in troubleshooting with the database server -zr and -zo options. Values can be combinations of the following, separated by either a plus sign (+), or a comma:

You can view the current setting for this property by executing the following query:

SELECT PROPERTY( 'RequestLogging' );

For more information, see List of database server properties.

See -zr database server option and Propriété de serveur RequestLogging.

The maximum size of the file used to record request logging information, in bytes. If you specify 0, then there is no maximum size for the request logging file, and the file is never renamed. This value is the default.

When the request log file reaches the size specified by either the sa_server_option system procedure or the -zs server option, the file is renamed with the extension .old appended (replacing an existing file with the same name if one exists). The request log file is then restarted.

See -zs database server option and Propriété de serveur RequestLogMaxSize.

The number of request log file copies to retain.

If request logging is enabled over a long period, the request log file can become large. The -zn option allows you to specify the number of request log file copies to retain.

See -zn database server option and Propriété de serveur RequestLogNumFiles.

Instructs the database server to maintain timing information for each new connection. This feature is turned off by default. When it is turned on, the database server maintains cumulative timers for all new connections that indicate how much time the connection spent in the server in each of several states. The change is only effective for new connections, and lasts for the duration each connection.

You can use the sa_performance_diagnostics system procedure to obtain a summary of this timing information, or you can retrieve individual values by inspecting the following connection properties:

• ReqCountUnscheduled
• ReqTimeUnscheduled
• ReqCountActive
• ReqTimeActive
• ReqCountBlockIO
• ReqTimeBlockIO
• ReqCountBlockLock
• ReqTimeBlockLock
• ReqCountBlockContention
• ReqTimeBlockContention

When the RequestTiming server property is on, there is a small overhead for each request to maintain the additional counters.

See -zt database server option and Propriété de serveur RequestTiming.

Allows you to manage secure features for a database server that is already running. The feature-list is a comma-separated list of feature names or feature sets. By adding a feature to the list, you limit its availability. To remove items from the list of secure features, specify a minus sign (-) before the secure feature name.

To call sa_server_option('SecureFeatures',...), the connection must have the ManageFeatures secure feature enabled on the connection. The -sf key (the system secure feature key) enables ManageFeatures, as well as all of the other features. So if you used the system secure feature key, then changing the set of SecureFeatures will not have any effect on the connection. But if you used another key (for example a key that had been created using the create_secure_feature_key system procedure) then your connection may be immediately affected by the change, depending on what other features are included in the key.

For the list of secure feature features, see -sf database server option

Any changes you make to allow or prevent access to features take effect immediately for the database server. The connection that executes the sa_server_option system procedure may or may not be affected, depending on the secure feature key the connection is using and whether or not it allows the connection access to the specified features.

For example, to secure two features, use the following syntax:

CALL sa_server_option('SecureFeatures', 'CONSOLE_LOG,WEBCLIENT_LOG' );

After executing this statement, the list of secure features is set according to what has been changed.

See -sf database server option and Creating secure feature keys.

The statistics cleaner fixes statistics that give bad estimates by performing scans on tables. By default the statistics cleaner runs in the background and has a minimal impact on performance.

Turning off the statistics cleaner does not disable the statistic governor, but when the statistics cleaner is turned off, statistics are only created or fixed when a query is run.

The name of the web service client log file. The web service client log file is truncated each time you use the -zoc server option or the WebClientLogFile property to set or reset the file name. Double any backslash characters in the path because this value is a string.

See -zoc database server option and Propriété de serveur WebClientLogFile.

This option enables and disables logging of web service clients. The information that is logged includes HTTP requests and response data. Specify ON to start logging to the web service client log file, and specify OFF to stop logging to the file.

See -zoc database server option and Propriété de serveur WebClientLogging.