In Dynamic Server, an UPDATE (or any other SQL data-manipulation language statement) that accesses a database of another database server can only reference the built-in data types that are not opaque, DISTINCT, extended, nor large-object types. Cross-server DML operations cannot reference a column or expression of an opaque, DISTINCT, complex, large-object, nor user-defined data type (UDT).
Distributed operations that access other databases of the local Dynamic Server instance, however, can also access most built-in opaque data types, which are listed in BOOLEAN and Other Built-In Opaque Data Types (IDS).
Updates across databases of the local Dynamic Server instance can also reference UDTs, as well as DISTINCT types based on built-in data types, if all the UDTs and DISTINCT types are explicitly cast to built-in data types, and all the UDTs, DISTINCT types, and casts are defined in each of the participating databases.
Updates cannot access the database of another database server unless both servers define TCP/IP connections in DBSERVERNAME or DBSERVERALIAS configuration parameters. This applies to any communication between Dynamic Server instances, even if both database servers reside on the same computer.
Enterprise Edition Home | Express Edition Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]