ALTER SERVER statement

Description

Modifies the attributes of a remote server.

Syntax

ALTER SERVER server-name 
[ CLASS 'server-class' ]
[ USING 'connection-info' ]
[ CAPABILITY 'cap-name' { ON | OFF } ]

Parameters

server-class:

{ASAJDBC | ASEJDBC | ASAODBC | ASEODBC | DB2ODBC | MSSODBC | ORAODBC | ODBC }

connection-info:

{ machine-name:port-number [/dbname ] | data-source-name }

cap-name:

the name of a server capability

Examples

Example 1

Usage

Changes made by ALTER SERVER do not take effect until the next connection to the remote server.

CLASS clause Use the CLASS clause to change the server class. For more information on server classes, see Chapter 17, “Server Classes for Remote Data Access” and Chapter 16, “Accessing Remote Data” in the Sybase IQ System Administration Guide.

USING clause The USING clause changes the server’s connection information. For more information about connection information, see CREATE SERVER statement.

CAPABILITY clause The CAPABILITY clause turns a server capability ON or OFF. Server capabilities are stored in the system table SYSCAPABILITY. The names of these capabilities are stored in the system table SYSCAPABILITYNAME. The SYSCAPABILITY table contains no entries for a remote server until the first connection is made to that server. At the first connection, Sybase IQ interrogates the server about its capabilities and then populates SYSCAPABILITY. For subsequent connections, the server’s capabilities are obtained from this table.

In general, you need not alter a server’s capabilities. It might be necessary to alter capabilities of a generic server of class ODBC.


Side Effects

Automatic commit is a side effect of this statement.

Standards

Permissions

Must have RESOURCE authority.

See also

CREATE SERVER statement

DROP SERVER statement

Chapter 17, “Server Classes for Remote Data Access,” and Chapter 16, “Accessing Remote Data,” in the Sybase IQ System Administration Guide