User's Manual

Chapter 14. Utilities and Options Reference
Separately licensable option required
Strong database encryption using AES_FIPS requires that you obtain the
separately-licensable SQL Anywhere Studio security option and is subject
to export regulations.
☞ To order this component, see “Separately-licensable components”
[Introducing SQL Anywhere Studio, page 5].
Specify encryption key (-ek) This option allows you to create a strongly
encrypted database by specifying an encryption key directly in the
command. The algorithm used to encrypt the database is AES or AES_FIPS
as specified by the -ea option. If you specify the -ek option without
specifying -ea, the AES algorithm is used.
Caution
Protect your key! Be sure to store a copy of your key in a safe location. A
lost key will result in a completely inaccessible database, from which there
is no recovery.
The following are invalid for database encryption keys:
♦ keys that begin with white space or single or double quotes
♦ keys that end with white space
♦ keys that contain semicolons
Prompt for encryption key (-ep) This option allows you to specify that
you want to create a strongly encrypted database by inputting the encryption
key in a dialog box. This provides an extra measure of security by never
allowing the encryption key to be seen in clear text.
You must input the encryption key twice to confirm that it was entered
correctly. If the keys don’t match, the initialization fails.
☞ For more information, see “Strong encryption” [SQL Anywhere Studio
Security Guide, page 15].
Extract fully qualified publications (–f) In most cases, you do not need to
extract fully qualified publication definitions for the remote database, since it
typically replicates all rows back to the consolidated database anyway.
However, you may want fully qualified publications for multi-tier setups or
for setups where the remote database has rows that are not in the
consolidated database.
Internal unload, internal load (–ii) Using this option forces the reload
script to use the internal UNLOAD and LOAD TABLE statements rather
309