|
In addition to bug fixes, Adaptive Server Anywhere version 6.0.3 includes new features in both the software and the documentation.
Combined stored procedure and Java debugger The Java debugger that was provided in previous releases has been upgraded. The new version of the debugger is able to debug not only Java classes within the database, but also SQL stored procedures and triggers.
For information on how to use the debugger, see Debugging Procedures, Functions, Triggers, and Events.
Read-only databases You can designate a database as read only when you start a database server. This feature makes deployment of databases on read-only media, such as CD-ROMs, more straightforward.
The ReadOnly database property returns On for read-only databases, and OFF for databases that are not being run in read-only mode.
For more information on read-only databases, see -r server option.
Computed column extensions New flexibility has been added to computed columns. You can now add computed columns to non-empty tables, and change the expression associated with a computed column. Computed columns are recalculated in a number of circumstances to ensure that the values are reliable.
For more information, see Working with computed columns, and Inserting and updating computed columns.
For information on syntax, see ALTER TABLE statement.
Support for the euro Collations have been added that include the euro currency symbol. These collations are the 1252LATIN1 and ISO9LATIN1 collations.
Additional collations Other collations have been added to the list of supplied collations, including 852POL (OEM Code Page 852 (Latin 2), with Polish ordering), 1250POL (Windows Latin2 code page 1250 with Polish ordering), 1250Latin2 (Windows Latin2 Code page 1250). 932JPN (Japanese), 936ZHO (similar to EUC_CHINA), and 950TAI (similar to EUC_TAIWAN).
For a complete list, see Choosing collations.
New Windows CE platforms The SH4 and ARM processors are now supported under Windows CE 2.1x.
ALTER TABLE extensions The ALTER TABLE statement has been extended to provide SQL/92-compliant clauses to set and drop defaults on columns. These clauses are an alternative to the existing MODIFY clause.
ALTER column-name SET DEFAULT default-value | ALTER column-name DROP DEFAULT
For more information, see ALTER TABLE statement.
LOAD TABLE extensions You can now load specific columns of a table using the LOAD TABLE statement. A new CHECK CONSTRAINTS option has been introduced to address rebuild issues.
For more information, see LOAD TABLE statement.
Easier connections across firewalls A set of protocol options has been introduced to allow easier connections across firewalls.
For more information, see Connecting across a firewall.
BACKUP statement extended The MATCH keyword has been introduced to allow renaming of the backup copy of the transaction log to a file name of the form YYMMDDnn.log. If you use this keyword, you can execute the same statement multiple times without writing over data.
For more information, see BACKUP statement.
Easier unload and reload The Unload [dbunload] utility has been enhanced (-ar option) to allow a single-step unload and reload of a database that can be used whether or not your database is involved in replication.
For more information, see Unload utility (dbunload), and Rebuilding databases.
Temporary file location The database server checks for a new environment variable, ASTMP, when deciding on the location of the temporary file. This allows you to use directories other than system temporary directories for the temporary file.
For more information, see SATMP environment variable.
New system procedures New system procedures allow DBA users to override some database server options (sa_server_option), and to flush the database server cache (sa_flush_cache).
For more information, see System procedures.
Character set conversion tuning You can control the application locale used in character set conversion for an individual connection using the new CharSet connection parameter.
For more information, see CharSet connection parameter [CS].
Re-organized Performance Monitor statistics The statistics made available to the Windows NT Performance Monitor have been organized into areas. Some statistics have been added, and ones of little use have been removed.
For a list of available statistics, see Monitoring statistics using Windows Performance Monitor.
Database properties from the utility database You can now execute SELECT statements, with no tables, against the utility database. This is primarily of use for retrieving database and connection properties.
For more information, see Using the utility database.
New database properties The following properties are available using the property function.
IsNetworkServer Returns YES if connected to a network database server, and NO if connected to a personal database server.
For more information, see Server-level properties.
DefaultCollation You can use the new DefaultCollation property to find the default collation to be used when creating a database.
For more information, see Determining the default collation, and Server-level properties.
MultiByteCharSet You can use the MultiByteCharSet database property to determine whether a database is using a multi-byte or single-byte collation.
For information on this property, see Database-level properties.
Support for some JDBC 2.0 functions in internal JDBC The internal server-side JDBC driver now supports functions from the JDBC 2.0 interface. Server-side Java applications can now use features such as such as scrollable, updatable result sets and batch updates. A side effect is that you can now access result sets from Java methods from Interactive SQL.
Using the main method in Java classes You can now execute a main method of a Java class from SQL.
For more information, see Calling the main method.
User-defined functions using Java classes You can wrap a Java method in a SQL user-defined function.
For more information, see CREATE FUNCTION statement.
Extensions to stored procedures using Java methods You can use OUT and INOUT parameters in stored procedures that are wrappers for Java methods.
For more information, see Returning values from Java via stored procedures.
Multi-threaded Java classes in the database Support has been added for the package java.lang.thread.
For more information, see Using threads in Java applications.
File access from Java Support has been added for all the classes in the package java.io, including those that enable file access from classes in the database. For security reasons, the java_input_output option has been introduced, which must be set by the DBA to enable this feature.
This feature is supported on Windows NT and UNIX.
CONVERT function extensions The date and time styles supported by the CONVERT function have been extended.
For more information, see CONVERT function [Data type conversion].
Database server startup dialog On 32-bit Windows operating systems, if you start a database server with no arguments, a window appears where you can specify a database file and additional parameters.
For more information, see Starting the database server.
Log Translation [dbtran] utility enhancements The Log Translation [dbtran] utility permits filtering of the transaction log operations to isolate subsets of operations.
For more information, see Log Translation utility (dbtran).
Transaction Log [dblog] utility enhancements The Transaction Log [dblog] utility now displays additional summary information, including offset information.
For more information, see Transaction Log utility (dblog).
Start Server in Background utility enhancements The Start Server in Background utility (dbspawn) has a -f option to force a server to start even if one is already running. This option uses a ForceStart connection parameter, used only by the db_start_engine Embedded SQL function.
For more information, see Start Server in Background utility (dbspawn), and db_start_engine function.
Replication Agent runs as a daemon On UNIX operating systems, you can run the Replication Agent as a daemon by supplying the -ud option.
For more information, see Log Transfer Manager utility (dbltm).