The sample output below shows the kind of information sp_configure prints if you have your display level set to “comprehensive” and you execute it with no parameters. The values it prints will vary, depending on your platform and on what values you have already changed.
sp_configure Group: Configuration Options Group: Backup/Recovery Parameter Name Default Memory Used Config Value Run Value Unit Type -------------- ------- ----------- ------------ --------- ---- ---- allow remote access 1 0 1 1 switch dyn print recovery info 0 0 0 0 switch dyn recovery interval in m 5 0 5 5 minutes dyn ...
All configuration groups and parameters will appear
in output if your display level is set to “comprehensive.”
Where:
The “Default” column displays the value Adaptive Server is shipped with. If you do not explicitly reconfigure a parameter, it retains its default value.
The “Memory Used” column displays the amount of memory used (in kilobytes) by the parameter at its current value. Some related parameters draw from the same memory pool. For instance, the memory used for stack size and stack guard size is already accounted for in the memory used for number of user connections. If you added the memory used by each of these parameters separately, it would total more than the amount actually used. In the “Memory Used” column, parameters that “share” memory with other parameters are marked with a hash mark (“#”).
The “Config Value” column displays the most recent value to which the configuration parameter has been set. When you execute sp_configure to modify a dynamic parameter:
The configuration and run values are updated.
The configuration file is updated.
The change takes effect immediately.
When you modify a static parameter:
The configuration value is updated.
The configuration file is updated.
The change takes effect only when you restart Adaptive Server.
The “Run Value” column displays the value Adaptive Server is currently using. It changes when you modify a dynamic parameter’s value with sp_configure and, for static parameters, after you restart Adaptive Server.
The “Unit” column displays the unit value in which the configuration parameter is displayed. Adaptive Server displays information in the following units:
Name of unit |
Unit description |
|---|---|
number |
Displays the number of items a parameter is configured for. |
clock ticks |
Number of clock ticks a parameter is set for. |
microseconds |
Number of microseconds for which a parameter is set. |
milliseconds |
Number of milliseconds for which a parameter is set |
seconds |
Number of seconds for which a parameter is set |
minutes |
Number of minutes for which a parameter is set |
hours |
Number of hours for which a parameter is set |
bytes |
Number of bytes for which a parameter is set |
days |
Number of days for which a parameter is set |
kilobytes |
Number of kilobytes for which a parameter is set |
megabytes |
Number of megabytes for which a parameter is set |
memory pages (2K) |
Number of 2K memory pages for which the parameter is set. |
virtual pages (2K) |
Number of 2K virtual pages for which the parameter is set. |
logical pages |
Number of logical pages for which the parameter is configured. This value depends on which logical page size your server is using; 2, 4, 8, or 16K. |
percent |
Displays the value of the configured parameter as a percentage. |
ratio |
Displays the value of the configured parameter as a ratio. |
switch |
Value of the parameter is either TRUE (the parameter is turned on or FALSE |
id |
ID of the configured parameter you are investigating. |
name |
Character string name assigned to the
run or configure value of the parameter. For example, the string “binary” appears
under the the run or configure value
column for the output of |
row |
Number of rows for which the specified parameter is configured. |
The “Type” column displays whether the configuration option is either static or dynamic. Changes to static parameters require that you restart Adaptive Server for the changes to take effect. Changes to Dynamic parameters take effect immediately without having to restart Adaptive Server.
