The file storage type prompt offers you choices about how to store the data in the file.
Table Datatype |
Storage Type |
---|---|
char, varchar |
c[har] |
text |
T[ext] |
int |
i[nt] |
smallint |
s[mallint] |
tinyint |
t[inyint] |
float |
f[loat] |
money |
m[oney] |
bit |
b[it] |
datetime |
d[atetime] |
binary, varbinary, timestamp |
x |
image |
I[mage] |
smalldatetime |
D |
real |
r |
smallmoney |
M |
numeric |
n |
decimal |
e |
The brackets [ ] in the table indicate that you can use the initial character or the beginning characters of the word. For example, for “bit” use “b,” “bi,” or “bit.”
To display this list while using bcp interactively, type a question mark (?) in response to the prompt Enter the file storage type.
The values that appear in the prompts are the defaults. Your response determines how the data is stored in the output file; you need not indicate the column’s type in the database table.
bcp fails if you enter a type that is neither implicitly convertible or char. For example, you may not be able to use smallint for int data (you may get overflow errors), but you can use int for smallint.
When storing noncharacter datatypes as their database types, bcp writes the data to the file in the SAP ASE server’s internal data representation format for the host operating system, rather than in human-readable form.
Before copying data that is in character format from a file into a database table, check the datatype entry rules in the Reference Manual: Building Blocks. Character data copied into the database with bcp must conform to those rules. If you do not specify the year first, dates in the undelimited (yy)yymmdd format may result in overflow errors.
When you send host data files to sites that use terminals different from your own, inform them of the datafile_charset that you used to create the files.