Returns a list of Adaptive Server attribute names and current values.
sp_server_info [attribute_id]
is the integer ID of the server attribute.
sp_server_info 12
attribute_id attribute_name attribute_value ------------ ------------------------- -------------------------- 12 MAX_OWNER_NAME_LENGTH 0
Returns the list of server attributes, described by the mandatory rows, and their values:
sp_server_info
The results set for sp_server_info is:
Column |
Datatype |
Description |
---|---|---|
attribute_id |
int |
NOT NULL. |
attribute_name |
varchar(60) |
NOT NULL. |
attribute_value |
varchar(255) |
The mandatory rows in the results set returned by sp_server_info are:
ID |
Server attribute name |
Description |
Value |
---|---|---|---|
1 |
DBMS_NAME |
Name of the DBMS. |
|
2 |
DBMS_VER |
The value used by the ODBC driver to determine version compatibility. Do not change the value of DBMS_VER. This is not the same as @@version, and the value must match the value used by the ODBC driver. |
Actual value |
6 |
DBE_NAME |
Unused |
|
10 |
OWNER_TERM |
Adaptive Server’s term for a table owner (the second part of a three-part name). |
|
11 |
TABLE_TERM |
Adaptive Server’s term for a table (the third part of a three-part name). |
|
12 |
MAX_OWNER_NAME_LENGTH |
Maximum length of the name for a table owner (the second part of a three-part name). |
|
13 |
TABLE_LENGTH |
The maximum number of characters for a table name. |
|
14 |
MAX_QUAL_LENGTH |
Maximum length of the name for a table qualifier (the first part of a three-part table name). |
|
15 |
COLUMN_LENGTH |
The maximum number of characters for a column name. |
|
16 |
IDENTIFIER_CASE |
The case sensitivity of user-defined names (table names, column names, and stored procedure names) in the database (the case in which these objects are presented in the system catalogs). |
|
18 |
COLLATION_SEQ |
The assumed ordering of the character set for this server. |
|
19 |
SAVEPOINT_SUPPORT |
Does the underlying DBMS support named savepoints? |
|
20 |
MULTI_RESULT_SETS |
Does the underlying DBMS or the gateway itself support multiple results sets (can multiple statements be sent through the gateway, with multiple results sets returned to the client)? |
|
22 |
ACCESSIBLE_TABLES |
In sp_tables, does the gateway return only tables, views, and so on, that are accessible by the current user (that is, the user who has at least select privileges for the table)? |
|
100 |
USERID_LENGTH |
The maximum number of characters for a user name. |
|
101 |
QUALIFIER_TERM |
Adaptive Server’s term for a table qualifier (the first part of a three-part name). |
|
102 |
NAMED_TRANSACTIONS |
Does the underlying DBMS support named transactions? |
|
103 |
SPROC_AS_LANGUAGE |
Can stored procedures be executed as language events? |
|
103 |
REMOTE_SPROC |
Can stored procedures be executed through the remote stored procedure APIs in DB-Library? |
|
104 |
ACCESSIBLE_SPROC |
In sp_stored_procedures, does the gateway return only stored procedures that are executable by the current user? |
|
105 |
MAX_INDEX_COLS |
Maximum number of columns in an index for the DBMS. |
|
106 |
RENAME_TABLE |
Can tables be renamed? |
|
107 |
RENAME_COLUMN |
Can columns be renamed? |
|
108 |
DROP_COLUMN |
Can columns be dropped? |
|
109 |
INCREASE_COLUMN_LENGTH |
Can column size be increased? |
|
110 |
DDL_IN_TRANSACTION |
Can DDL statements appear in transactions? |
|
111 |
DESCENDING_INDEXES |
Are descending indexes supported? |
|
112 |
SP_RENAME |
Can a stored procedure be renamed? |
|
500 |
SYS_SPROC_VERSION |
The version of the catalog stored procedures currently implemented. |
|
Any user can execute sp_server_info.