Case sensitivity and database options   The SET OPTION statement and CONNECTION_PROPERTY function use case insensitive option names. However, in databases that use a Turkish collation or are case sensitive, option names referenced in queries should be written using the case specified in Alphabetical list of options.

In either of these situations, executing a query on SYSOPTION or a query like the following may not match any rows if the option name is used with the wrong case:

SELECT * 
   FROM sa_conn_properties() 
   WHERE propname = 'BLOCKING'

Using embedded SQL with ansi_blanks set to On   For embedded SQL with ansi_blanks set to On and a blank padded database, when you supply a value of data type DT_STRING, you must set the sqllen field to the length of the buffer containing the value (at least the length of the value plus space for the terminating null character).

When a database is blank padded, the ansi_blanks option controls truncation warnings sent to the client if the expression being fetched is CHAR or NCHAR (not VARCHAR or NVARCHAR) and it is being fetched into a char or nchar (not VARCHAR or NVARCHAR) host variable. See ansi_blanks option [compatibility].

ansi_integer_overflow option default setting changed   When a new database is created, the default value for the ansi_integer_overflow database option is On. In previous versions of the software, the default value for this option was Off.

date_format option changes   The date_format option no longer supports the following values when specifying the format string:

Also, if the character data is multibyte, the length of each symbol now reflects the number of characters. For example, the 'mmm' symbol specifies a length of three characters for the month. In previous versions, the length of the symbol reflected the number of bytes. See date_format option [compatibility].

login_mode database option   The value Mixed is deprecated for the login_mode database option. Specify Standard,Integrated to allow both standard and integrated logins. See login_mode option [database].

string_rtruncation option default setting changed   When a new database is created, the default value for the string_rtruncation database option is On. In previous versions of the software, the default value for this option was Off. See string_rtruncation option [compatibility].

If you use the CAST function to truncate strings, the string_rtruncation database option must be set to Off; otherwise, there will be an error.

It is recommended that you use the LEFT function to truncate strings. See LEFT function [String].

temp_space_limit_check option default setting changed   The default setting for the temp_space_limit_check option has been changed to On. Now, by default, if a connection requests more than its quota of temporary file space, then the request fails and the error SQLSTATE_TEMP_SPACE_LIMIT is returned. See temp_space_limit_check option [database].

timestamp_format option changes   The timestamp_format option no longer supports the use of French days and months. Also, if the character data is multibyte, the length of each symbol now reflects the number of characters. For example, the 'mmm' symbol specifies a length of three characters for the month. In previous versions, the length of the symbol reflected the number of bytes. See timestamp_format option [compatibility].

truncate_date_values option removed   The truncate_date_values option has been removed. In previous releases, this option allowed you to include a time in columns defined using the DATE data type. In this release, columns defined with DATE can only contain dates. If you want to store dates and times, use the TIMESTAMP data type. See TIMESTAMP data type.