Storing transfer information

Transfer information is stored in:

spt_TableTransfer

The results of successful transfers retrieved from the table specified in the transfer table command are used as the defaults for subsequent transfers. For example, if you issue this command (including row and column separators):

transfer table mytable for csv

The next time you transfer table mytable, the transfer command, by default uses for csv and the same row and column separators.

Each database has its own version of spt_TableTransfer. The table stores history only for table transfers for tables in its same database that are marked for incremental transfer.

The max transfer history configuration parameter controls how many transfer history entries Adaptive Server retains in the spt_TableTransfer table in each database. See Chapter 5, “Setting Configuration Parameters,” in the System Administration Guide, Volume 1.

Database owners use sp_setup_table_transfer to create the spt_TableTransfer table. sp_setup_table_transfer takes no parameters, and works in the current database.

spt_TableTransfer stores historical information about both successful and failed transfers. It does not store information for in-progress transfers.

spt_TableTransfer is a user table, rather than a system table. It is not created when you create Adaptive Server, but Adaptive Server automatically creates it in any database that has tables that are eligible for transfer, if you do not use sp_setup_transfer_table to manually create it (creating it manually may allow you to avoid unexpected errors that can occur when Adaptive Server creates the table automatically).

sp_help reports incremental transfer as a table attribute.

The columns in spt_TableTransfer are:

Column

Datatype

Description

end_code

unsigned smallint not null

The transfer’s ending status.

0 – success.

error code – failure.

id

int not null

The object ID of the transferred table.

ts_floor

bigint not null

The beginning transaction timestamp.

ts_ceiling

bigint not null

The transaction timestamp after which rows are uncommitted, and therefore not transferred.

time_begin

datetime not null

  • The date and time the transfer began, or

  • The time Adaptive Server began to set up the command if the transfer fails before implementation. Otherwise, this is the time at which the command sent the first data to the output file.

time_end

datetime not null

  • The date and time the transfer ended, or

  • If the transfer command fails, this is the time of failure. Otherwise, this is the time at which the command finishes sending data and closes the file

row_count

bigint not null

The number of rows transferred.

byte_count

bigint not null

The number of bytes written.

sequence_id

int not null

A number that tracks this transfer, unique to each transfer of a table.

col_order

tinyint not null

A number representing the column order of the output:

  • 1 – id

  • 2 – offset

  • 3 – name

  • 4 – name_utf8

output_to

tinyint not null

A number representing the output format:

    • 1 – ase

    • 2 – bcp

    • 3 – csv

    • 4 – iq

tracking_id

int null

An optional customer-supplied tracking ID. If you do not use with tracking_id = nnn, this column is null.

pathname

varchar (512) null

The output file name.

row_sep

varchar (64) null

The row separator string used for for csv.

col_sep

varchar(64) null

The column separator used for for csv.

monTableTransfer

monTableTransfer table provides:

See monTableTransfer in the Reference Manual: Tables.