Component Integration Services supports a number of classes.
Each server class has a set of unique characteristics that system administrators and
programmers need to know about in order to configure the server for remote data access.
These properties are:
Types of servers that each server class supports
Datatype conversions specific to the server class
Restrictions on Transact-SQL statements that apply to the server class
dbcc Commands
All dbcc commands used by Component Integration Services are available with a single dbcc entry point.
Functions
When a SQL statement such as a select, insert, delete, or update contains a built-in function, Component Integration Services must determine if the function can be forwarded to the remote server, or if it must be evaluated within the local server using remote data.
Transact-SQLCommands
If Component Integration Services does not pass all of a command’s syntax to a remote server (such as all clauses of a select statement), the syntax that is passed along is described for each server class.
Passthrough Mode
Passthrough mode is provided within Component Integration Services as a means of enabling a user to perform native operations on the server to which the user is being “passed through.”
Delimited Identifier Support
The behavior of bracketed identifiers is identical to quoted identifiers, with the exception that you do not need to set quoted_identifier on in order to use them.
auto identity Option
When the auto identity database option is enabled, an IDENTITY column is added to any tables that are created in the database.
Triggers
Component Integration Services allows triggers on proxy tables; however, their usefulness is limited. You can create a trigger on a proxy table and the trigger is invoked just as it would be for a normal SAP ASE table.
Created June 25, 2014. Send feedback on this help topic to Technical Publications:
pubs@sap.com