The default user ID for demo.db and newly created databases is DBA and the default password is sql. The user ID is case-insensitive and the password is case-sensitive. You should change the password before deploying the database.

For more information about default user IDs and passwords, see DBA authority.

For information about failed login attempts for DBA users, see DBA authentication.

A lost or forgotten DBA password cannot be recovered. If you require assistance, contact Technical Support ( http://www.sybase.com/support).

The connection parameters required to connect to a database vary depending on the location of the application relative to the database server. The following connection scenarios assume that there is no communication encryption and there is only one database running on a database server.

In the following examples, you connect to the SQL Anywhere sample database, %SQLANYSAMP12%\demo.db using Interactive SQL.

See Connecting to the sample database on Unix.

See Connecting to the sample database on Mac OS X.

Databases created with SQL Anywhere 9.0.1 or later include the SYSHISTORY system view. The rows in this view that reflect INIT and UPDATE operations give information about when, and with what version, the database was created and upgraded. See SYSHISTORY system view.

To determine the version without starting the database, see DBCreatedVersion method [database tools].

Execute the following statement to the names of the databases running on a server:

SELECT DB_NAME(Number) FROM sa_db_list();

Execute the following statement to return a number of databases running on a server:

SELECT * FROM sa_db_list();

See sa_db_list system procedure and DB_NAME function [System].

Yes, you can install multiple major versions of SQL Anywhere on the same computer. For example, SQL Anywhere 9.0.2, 10.0.1, 11.0.1, and 12.0.1 can all be installed and run independently.

However, you must use caution when starting a SQL Anywhere executable that has the same name in multiple versions (for example, dbisql or dbinit) to ensure that you are starting the correct version of the application. You can either specify the full absolute path using environment variables such as SQLANY12, or ensure the version of SQL Anywhere you want is specified first in your path.

See Utility versions and the upgrade process.

You should run multiple databases on a single database server because this configuration optimizes the use of computer resources.

Having multiple database servers running on the same computer may result in a competition for resources, and (with dynamic cache resizing) this configuration may result in degraded or unpredictable performance. Degraded or unpredictable performance may be acceptable if you need to stop one database server for maintenance without affecting the others, or if you need to isolate errors to a single database server.

You should verify that you are correctly licensed for the installation option that you choose. For more information, see Multiple databases running on a single database server.

See Understanding unexpected changes in the database size.

See the following:

• Backup and recovery plan design
• See the tech note titled What Backup, Recovery, and Disaster Recovery Mean to Your SQL Anywhere Databases ( http://www.sybase.com/detail?id=47877)

See the tech note titled "I've Got An Assertion! What Should I Do?" ( http://www.sybase.com/detail?id=1010805).

To report low priority SQL Anywhere bugs, log in to  http://case-express.sybase.com. Bugs reported using Case-Express are assigned a lower priority than cases opened through Technical Support.

For priority issues, open a support case with Technical Support ( http://www.sybase.com/support).

See the following documents:

• Performance monitoring and diagnostic tools
• Tips for improving performance
• Diagnosing Application Performance Issues with SQL Anywhere ( http://www.sybase.com/detail?id=1060302)
• Capacity Planning with SQL Anywhere ( http://www.sybase.com/detail?id=1056535)

See SQL Anywhere Server upgrades.

SQL Anywhere performs best when the database is created with the same major version as the database server. Rebuild the database if you are experiencing performance problems and no longer need to run the database on earlier versions of SQL Anywhere. See Database rebuilds and Performance monitoring and diagnostic tools.

SQL Anywhere developers strive to ensure that applications continue to work after an upgrade. However, your application may be affected by behavior changes and the removal of previously supported features.

To determine if behavior changes have been made to your version of SQL Anywhere, or if features have been removed or deprecated, select the section relevant to your version of SQL Anywhere. See SQL Anywhere 12 - Changes and Upgrading.

If your JDBC applications do not work after applying an EBF, it is likely because you had either Interactive SQL, Sybase Central, the fast launchers, or other JDBC applications running when the EBF was applied. Shutting down all JDBC-based applications and reapplying the EBF may resolve the problem. See Ensure JDBC applications are not running when applying an EBF.

See the tech note SQL Anywhere Supported Platforms and Engineering Support Status ( http://www.sybase.com/detail?id=1002288).

For descriptions of the different licensing options for SQL Anywhere 10 and later, including examples that show you how to apply your license, see SQL Anywhere Licensing  (http://www.sybase.com/detail?id=1056242).

The size of the database that can be supported by SQL Anywhere is dependent on the memory, CPU, and disk drive capacity of the computer on which SQL Anywhere is installed. See SQL Anywhere size and number limitations.

A number of our customers discuss the implementation of large databases in the SQL Anywhere Forum. See the forum thread  http://sqlanywhere-forum.sybase.com/questions/92/whats-the-size-of-your-biggest-database.

To migrate to SQL Anywhere, you must import your data into a SQL Anywhere database. See Database migration to SQL Anywhere.

There are differences between products, such as different dialects of SQL, so your application may need to be modified.

See "Choosing SQL Anywhere for ISV Applications" ( http://www.sybase.com/detail?id=1053363).

See Create a graphical plan with detailed and node statistics.

No. The OUTPUT statement can only be executed in Interactive SQL and cannot be used within a stored procedure. Use the UNLOAD statement within your stored procedure to save the result set generated by a SQL statement to a text file. If you use the UNLOAD statement in your stored procedure, information is unloaded from the database server and not from the client computer from which the statement was executed. See UNLOAD statement.

See List of SQL Anywhere tutorials.

See the SQL Anywhere OnDemand Edition documentation at  http://dcx.sybase.com/cloud100.

See:

• SQL Anywhere documentation:  dcx.sybase.com/dcx_home.html
• SQL Anywhere v10 / v9.0.2 Frequently Asked Questions ( http://www.sybase.com/detail?id=1053692)
• SQL Anywhere 11.0.1 FAQs ( http://www.sybase.com/detail?id=1062382)
• SQL Anywhere Studio/Adaptive Server Anywhere Patches and Upgrades FAQ ( http://www.sybase.com/detail?id=1019567)
• SQL Anywhere Web Edition FAQ ( http://www.sybase.com/detail?id=1057560)
• SQL Anywhere blogs ( http://iablog.sybase.com/sqlanyblogs.php)
• SQL Anywhere Forum ( http://sqlanywhere-forum.sybase.com/