ANSI-Compliant Databases

The following example creates an ANSI-compliant database:

CREATE DATABASE employees WITH LOG MODE ANSI; 

ANSI-compliant databases are different from databases that are not ANSI compliant in several ways, including the following features:

• All SQL statements are automatically contained in transactions.
• All databases use unbuffered logging.
• Owner naming is enforced.

  You must qualify with the owner name any table, view, synonym, index, or constraint that you do not own. Unless you enclose the owner name between quotation marks, alphabetic characters in owner names default to uppercase. (To prevent this upshifting of lowercase letters in undelimited owner names, you can set the ANSIOWNER environment variable to 1.)

  In addition, the routine signature of a UDR includes the name of the owner; in databases that are not ANSI compliant, this is true only for the sysdbopen( ) and sysdbclose( ) procedures.

• For sessions, the default isolation level is REPEATABLE READ.
• Default privileges on objects differ from those in databases that are not ANSI compliant. When you create a table or a synonym, other users do not receive access privileges (as members if the PUBLIC group) on the object by default.
• All DECIMAL data types are fixed-point values. If you declare a column as DECIMAL(p), the default scale is zero, meaning that only integer values can be stored. (In a database that is not ANSI compliant, DECIMAL(p) is a floating-point data type of a scale large enough to store the exponential notation for a value.)