Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 10.0.1 » UltraLite - Database Management and Reference » Creating and Configuring UltraLite Databases

UltraLite on-device creation Next Page

Choosing creation-time database properties for UltraLite


UltraLite database creation properties, written to the database via all administration tools or even the CreateDatabase function, are recorded as name=value pairs. UltraLite stores these properties in system tables, which means that users and/or applications can access them in the same way. See sysuldata system table.

Accessing properties

You cannot change properties after you have created a database. However, you can view them in Sybase Central. See Viewing UltraLite database settings and modifying database options.

You can also access them programmatically from the UltraLite application. Typically, applications should not access the data in these tables directly. Instead, your applications should call the GetDatabaseProperty function appropriate to the API.

For API specific details, see:

In addition to these properties, you can further configure other aspects of your database with either database options or connection parameters. See:

Property listDescription

case

Sets the case-sensitivity of string comparisons in the UltraLite database. See UltraLite case sensitivity considerations and UltraLite case property.

checksum_level

Sets the level of checksum validation in the database. See Verifying page integrity with checksums and UltraLite checksum_level property.

collation

Sets the collation used by the database. See UltraLite character considerations and UltraLite collation property.

date_format

Sets the default string format in which dates are retrieved from the database. See UltraLite date considerations and UltraLite date_format property.

date_order

Controls the interpretation of date ordering of months, days, and years. See UltraLite date considerations and UltraLite date_order property.

fips

Controls AES FIPS compliant data encryption using a Certicom certified cryptographic algorithm. See UltraLite security considerations and UltraLite fips property.

max_hash_size

Set the maximum number of bytes that are used to hash the UltraLite indexes. See UltraLite index performance considerations and UltraLite max_hash_size property.

nearest_century

Controls the interpretation of two-digit years in string-to-date conversions. See UltraLite nearest century conversion considerations and UltraLite nearest_century property.

obfuscate

Controls whether or not to obfuscate data in the database. Obfuscation is a form of simple encryption. See UltraLite security considerations and UltraLite obfuscate property.

page_size

Defines the database page size. See UltraLite page size considerations and UltraLite page_size property.

precision

Specifies the maximum number of digits in the result of any decimal arithmetic. See UltraLite decimal point position considerations and UltraLite precision property.

scale

Specifies the minimum number of digits after the decimal point when an arithmetic result is truncated to the maximum precision. See UltraLite decimal point position considerations and UltraLite scale property.

time_format

Sets the format for times retrieved from the database. See UltraLite time considerations and UltraLite time_format property.

timestamp_format

Determines how the timestamp is formatted in UltraLite. See UltraLite timestamp considerations and UltraLite timestamp_format property.

timestamp_increment

Determines how the timestamp is truncated in UltraLite. See UltraLite timestamp considerations and UltraLite timestamp_increment property.

utf8_encoding

Encodes data using the UTF-8 format, 8-bit multibyte encoding for Unicode. See UltraLite character considerations and UltraLite utf8_encoding property.


UltraLite character considerations
UltraLite index performance considerations
UltraLite case sensitivity considerations
UltraLite date considerations
UltraLite time considerations
UltraLite timestamp considerations
UltraLite nearest century conversion considerations
UltraLite decimal point position considerations
UltraLite page size considerations
UltraLite security considerations