IMXFER Procedure

TABLE Statement

The TABLE statement is used to specify the table to export from one server and import to another server.

Syntax

Required Arguments

Optional Argument

TABLE Statement Options

Syntax

TABLE export-server-name export-table-name import-server-name <import-table-name> </ options>;

Required Arguments

export-server-name

specifies the name to use for the server instance that is exporting the table.

export-table-name

specifies the in-memory table to export. The name is specified as server-tag.member-name.

import-server-name

specifies the name to use for the server instance that is importing the table.

Optional Argument

import-table-name

specifies the name to use for the imported table.

If you do not specify a name, then the IMXFER procedure attempts to create a table with the same name as the exported table. If a table with the same name already exists in the importing server, then the transfer fails.

If you specify a table name, prefix the table name with the tag that you want to use for accessing the table. For example, HPS and USER.SASDEMO can be used as tags for a table name. For more information, see Understanding Server Tags.

TABLE Statement Options

DELETED= INCLUDE | INC | EXCLUDE

specifies how rows that are marked for deletion are handled in the transfer. By default, DELETED=EXCLUDE, which implies that any row that has a deletion mark is not transferred.

If you specify DELETED=INCLUDE, the IMXFER procedure instructs the server to ignore the deletion marks. Any rows that are marked for purging are not transferred, regardless of the DELETED= option.

Default

EXCLUDE

WHERE="where-expression"

specifies the WHERE clause to apply to the exported table. Only rows that meet the conditions of the WHERE expression are transferred.

Alias

FILTER=

PARTITION= NO | REMOVE | YES

specifies how to handle partitioning (and ordering within the partitions) when a partitioned table is transferred. By default, PARTITION=YES, and implies that a partitioned table is transferred to the importing server and remains partitioned and ordered by the same variables. When the servers have different numbers of worker nodes, there is no guarantee that partitions end up on the same nodes. However, it is guaranteed that partitions appear together on a node in the importing server.

Partitioning incurs some overhead and if you transfer a table from a smaller to a larger number of nodes, you might not want to apply partitioning. (Removing the partitioning spreads the data out more evenly in the importing server.) Or, you might not want to maintain partitioning on transfer if the transfer is for archival purposes. In that case, specify PARTITION=NO or PARTITION=REMOVE. This transfers the table to the importing server without the partitioning information.

Default

YES

PERM=mode

specifies the permission setting for accessing the imported table. The mode value is specified as an integer value such as 755. The mode corresponds to the mode values that are used for UNIX file access permissions.

For Windows servers, the UNIX mode setting is not applicable. Access is controlled according to permissions that you set manually on the signature files directory.

Alias	PERMISSION=
Range	600 to 777