What's New in SQL Anywhere Studio
What's New in Version 8.0.2
Behavior changes in version 8.0.2
The following is a list of behavior changes from previous versions of the software.
Windows CE 2.11 no longer supported Support has been dropped for the Windows CE 2.11 platform.
SH3 and SH4 chips no longer supported Support for Windows CE devices using the SH3 and SH4 chips has been dropped.
For a list of supported platforms, see Operating system versions, and Windows and NetWare operating systems.
OPTIMIZATION_GOAL setting The default setting for the OPTIMIZATION_GOAL option is set to all-rows rather than first-row. This affects the execution plan chosen for some queries and so will change performance characteristics.
For more information, see OPTIMIZATION_GOAL option [database].
xp_cmdshell displays a command window on Windows operating systems It is now possible to control whether xp_cmdshell starts a new window. The behavior change applies to databases created with or upgraded to version 8.0.2 or later. On older databases, the previous behavior of not displaying a command window is maintained. The new behavior is compatible with other databases such as Adaptive Server Enterprise and Microsoft SQL Server.
You can hide the command window by specifying a second parameter in the call to xp_cmdshell.
For more information, see xp_cmdshell system procedure.
Full-length English day names are recognized regardless of the language used by the database server When creating events, the full-length English day names are recognized by the database server, regardless of the language (German, Chinese, etc.) the database server is using. This means that event definitions in the reload script will be recognized by a server running with a different language.
Events that use the abbreviated English day names (Mon, Tue, and so on) are not recognized by servers running in languages other than English.
For more information, see CREATE EVENT statement.
OPTION settings validated Integer options with minimum and maximum values are now validated. Setting an option to an invalid value gives the error Invalid setting for option '%1'.
If you unload and reload a database that contains invalid option settings, they are set to the closest legal value.
The affected options are as follows. The square brackets indicate an inclusive range.
| Option | Range |
|---|---|
| ISOLATION_LEVEL | [ 0, 3 ] |
| PRECISION | [ 0, 127 ] |
| SCALE | [ 0, 127 ] |
| NEAREST_CENTURY | [ 0, 100 ] |
| MAX_HASH_SIZE | [ 2, 64 ] |
| MAX_WORK_TABLE_HASH_SIIZE | [ 2, 64 ] |
| FIRST_DAY_OF_WEEK | [ 1, 7 ] |
| DEFAULT_TIMESTAMP_INCREMENT | [ 1, 60 000 000 ] |
Renamed joins The names of two joins have changed, both in the graphical plan and in the documentation. Nested loops join not exists (JNE) are now called Nested loops antisemijoin (JNLA), and nested loops exists joins (JE) are now called nested loops semijoins (JNLS)
For more information, see Join algorithms.
This list includes features that are no longer supported and that impact existing applications.
-d server option deprecated on Windows When used on NetWare, the -d option forces the use of POSIX I/O rather than DFS (Direct File System) I/O. In Windows, the option is still allowed on the command line, but is ignored.
For more information, see -d server option.