Sybase DC38133-01-0902-01 manual Operations not replicated in passthrough mode, 262

	♦ Resynchronize users.
	♦ Drop users from the setup.
	♦ Change the address, message type, or frequency for a remote user.
	♦ Add a column to a table.
	Many other schema changes are likely to cause serious problems if executed
	on a running SQL Remote setup.
Passthrough works on	In a multi-tier SQL Remote installation, it becomes important that
only one level of a	passthrough statements work on the level of databases immediately beneath
hierarchy	the current level. In a multi-tier installation, passthrough statements must be
	entered at each consolidated database, for the level beneath it.
Operations not replicated in passthrough mode
	There are special considerations for some statements in passthrough mode.
Calling procedures	When a stored procedure is called in passthrough mode using a CALL or
	EXEC statement, the CALL statement itself is replicated and none of the
	statements inside the procedure are replicated. It is assumed that the
	procedure on the replicate side has the correct effect.
Control of flow	Control-flow statements such as IF and LOOP, as well as any cursor
statements and cursor	operations, are not replicated in passthrough mode. Any statements within
operations	the loop or control structure are replicated.
	Operations on cursors are not replicated. Inserting rows through a cursor,
	updating rows in a cursor, or deleting rows through a cursor are not
	replicated in passthrough mode.
	Static embedded SQL SET OPTION statements are not replicated. The
	following statement is not replicated in passthrough mode:
	EXEC SQL SET OPTION . . .
	However, the following dynamic SQL statement is replicated:
	EXEC SQL EXECUTE IMMEDIATE "SET OPTION . . .	"
Batches	Batch statements ( a group of statements surrounded with a BEGIN and
	END) are not replicated in passthrough mode. You receive an error message
	if you try to use batch statements in passthrough mode.

262