Following is a list of enhancements made to database utilities in SQL Anywhere version 11.0.0.
Configuration file enhancement You can now use an ampersand (&) in configuration files to indicate that the previous token is continued on the next line. See Using configuration files.
A new option, -cp, has been added to allow you to cause dbunload to compress the data output file.
Previously, if specified the -ek, -ep, or -ea encryption options, without also specifying the -an or -ar reload options, an error was returned. Now, however, dbunload accepts the encryption options, and applies them to the output file it creates.
The -g option now refreshes text indexes defined as MANUAL REFRESH. See Text indexes.
By default, text indexes defined as MANUAL REFRESH are not initialized as part of a reload. If you want to initialize these text indexes, you can specify the dbunload -g option.
The -no option lets you unload object definitions in alphabetical order, grouped by object type. This can be useful for comparing the reload.sql files for databases.
When a database is autostarted by running the Validation utility, it is started in read-only mode. This prevents you from changing the database in case it is being validated as part of a backup and recovery plan.
Maintaining the generated .sql file if the Log Translation utility (dbtran) detects corruption The Log Translation utility -k option lets you specify that you do not want a partial .sql file deleted if translating the log file fails because of corruption in the transaction log file. See Log Translation utility (dbtran).
|Discuss this page in DocCommentXchange.
Send feedback about this page using email.
|Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|