What's New in SQL Anywhere Studio
What's New in Version 7.0.0
Behavior changes in version 7.0.0
This list includes features that are no longer supported and that impact existing applications.
Windows 3.x and Windows CE 2.0 no longer supported Windows 3.1 and Windows 3.11 are no longer supported. Windows CE 2.0 is no longer supported.
DDE protocol no longer supported The DDE protocol was used to communicate from 16-bit Windows 3.x applications to a Windows 95/98 database server on the same machine. It is no longer required: Windows 3.x applications based on older versions of the software can use TCP/IP to communicate with the version 7.0 database server.
IPX protocol deprecated Although communications using IPX are still supported in the present release, it is highly recommended that you use the SPX protocol instead. The communications parameters are the same as for IPX, and performance is better. Support for IPX will be dropped in a future release.
By default, both the database server and the client software do not start the IPX protocol unless you instruct it to do so explicitly using the -x option or the CommLinks connection parameter. The SPX protocol is started by default.
For information on using SPX from the client side, see CommLinks connection parameter [LINKS]. For information on using SPX from the server side, see -x server option.
Deprecated network communication parameters The Broadcast and CommAutoStop communication parameters are still allowed, but have no effect. They will not be supported in future versions of Adaptive Server Anywhere.
No dbclient compatibility executable In version 6, the dbcli6.exe utility provided easier compatibility with version 5 client connection methods. There is no comparable utility in version 7.
This list includes behavior changes in existing features that may impact applications or have an impact during development or database management.
Interactive SQL changes The new version of Interactive SQL has some changes from previous versions. As it is an interactive tool, most do not need documentation.
The supported formats for INPUT and OUTPUT statements have changed, and now include:
INPUT ASCII, DBASE, DBASEII, DBASEIII, EXCEL, FIXED, FOXPRO, LOTUS
OUTPUT ASCII, DBASE, DBASEII, DBASEIII, EXCEL, FIXED, FOXPRO, HTML, LOTUS, SQL
Server name space change It is now disallowed for more than one database server with the same name to be running on TCP/IP anywhere on the network. Previously, multiple servers with the same name were allowed as long as they were on separate ports.
Mirrored logs deleted when DELETE_OLD_LOGS is ON Previously, any mirror of an old transaction log was not deleted, although the primary copy of the old transaction log was deleted.
ODBC SQLDescribeCol behavior A SQLDescribeCol call on the @@identity field now returns SQL_BIGINT. In earlier versions, it returned SQL_INTEGER.
Update constraints A new ANSI_UPDATE_CONSTRAINTS option has been added. Setting this option to CURSORS, or STRICT, restricts updates to those allowed by the ANSI standard. Setting this option to OFF, which is the historical behavior, allows a greater range of updates.
For more information, see ANSI_UPDATE_CONSTRAINTS option [compatibility], and UPDATE statement.
Identifier length limit Long identifiers are treated more consistently than in the past. Identifiers longer than 128 bytes were sometimes accepted and sometimes not, depending on the type of database object being named. Now any attempt to define identifiers longer than 128 bytes reports an error.
For more information, see Identifiers.
jConnect connections If you use the REMOTEPWD field to connect via jConnect to a named database on an Adaptive Server Anywhere database server, you must assign the field in a different manner for jConnect version 4.2 and above, included with this software.
For more information, see Supplying a URL for the server.
User-defined errors Within procedures and triggers, you can declare exceptions in the range 99000 to 99999 as user-defined errors in compound statements. You can use the SIGNAL statement to handle these errors.
For more information, see BEGIN statement, and SIGNAL statement.
LOAD TABLE and UNLOAD TABLE security A database server option has been added to control the permissions required to execute the LOAD TABLE and UNLOAD TABLE statements.
For more information, see -gl server option.
@@identity in triggers If a table (T1) with an autoincrement column has an insert trigger which causes an insert into a second table (T2) also having an autoincrement column, it was not previously possible to obtain the autoincrement value assigned for T1 after the insert had completed. At that point, the value of @@identity would be the value assigned to T2. The behavior of @@identity has been altered to make the value accessible.
For the new behavior of @@identity within triggers, see @@identity global variable.
Embedded SQL DECL_FIXCHAR In previous releases, the SQL preprocessor converted a type DECL_FIXCHAR to an array. For example, DECL_FIXCHAR(12) was converted to char name_fixchar[12].
In the current release, the SQL preprocessor converts DECL_FIXCHAR declarations to DECL_FIXCHAR(12) name_fixchar, and references are of the form name_fixchar.array[i].