Following is a list of product-wide additions introduced in version 10.0.0.
Product name changed to SQL Anywhere 10 SQL Anywhere Studio has been renamed SQL Anywhere 10, and Adaptive Server Anywhere has been renamed SQL Anywhere. Many names of files, directories, services, and executables have consequently changed, mostly to reflect the change from ASA to SA. These changes are detailed in the relevant Behavior Change topics of this chapter.
New install for DataWindow.NET DataWindow.NET is a custom control tool that is useful to database developers using Visual Studio. It is provided as an optional component during your SQL Anywhere installation. Complete documentation is provided in the installation.
RSA now included with SQL Anywhere You no longer have to purchase a separate license to use RSA encryption. See Transport-Layer Security.
Feature statistics collection SQL Anywhere 10 tracks information about the computer running the software, such as the operating system, the options use to start the database server, the SQL Anywhere 10 software build being used, and so on, as well as information about the SQL Anywhere 10 features being used. If a fatal error occurs, the software automatically prompts you to send any information about the problem, as well as the SQL Anywhere feature statistics to iAnywhere. This information can be used to help diagnose the problem, should you open a technical support case. See Error reporting in SQL Anywhere.You also have the option of sending the feature statistics at any time using the SQL Anywhere Support utility (dbsupport). The feature statistics information helps iAnywhere understand how the product is being used to help improve the software. See SQL Anywhere Support utility (dbsupport). The SADIAGDIR environment variable specifies the location of the directory where crash reports and feature statistics are stored. See SADIAGDIR environment variable.
Error reporting When an internal error occurs in Sybase Central, Interactive SQL, or the SQL Anywhere Console utility, a log of the error is written to the hard drive and a dialog appears where you can choose to send the error report to iAnywhere.In addition, if a fatal error occurs in any of the following: personal server, network server, MobiLink server, dbmlsync, MobiLink Listener, QAnywhere agent, SQL Remote, or Replication Agent, a log of the error is written to the hard drive and a dialog appears where you can choose to send the error report to iAnywhere. The SQL Anywhere Support utility (dbsupport) can be configured to automatically submit these error reports. See SQL Anywhere Support utility (dbsupport). If you choose not to submit an error report, the file remains in the diagnostic directory on your hard disk. The SADIAGDIR environment variable specifies the location of the directory where crash reports and feature statistics are stored. See SADIAGDIR environment variable.
Control which features are available in the administration tools You can now control which features are available for users in the administration tools using an OEM.ini file located in the same directory as the tool's .jar file.
Using SQL Anywhere 10 on Windows Vista The following known issues exist on Windows Vista:
Updating license information with the Server Licensing utility (dblic.exe) fails unless you have administrator privileges or write permissions on the directory containing the server executables.
There is a known problem with using shared memory when running SQL Anywhere as a service or an unprivileged account. This problem is under investigation. As an alternative, you can use TCP/IP.