Starting the database server

The general form for the server command is as follows:

executable [ server-options ] [ database-file [ database-options ], ...]

If you supply no options and no database file, then on Windows operating systems a window appears, allowing you to browse to your database file.

The elements of the database server command include the following:

  • Executable   The personal server (dbeng11) or the network server (dbsrv11).

    For more information about the executable names on different operating systems, see Introduction to running SQL Anywhere database servers.

  • Server options   These options control the behavior of the database server for all running databases.

  • Database file   You can specify zero, one, or more database file names. Each of these databases starts and remains available for applications.

    Caution

    The database file and the transaction log file must be located on the same physical computer as the database server or accessed via a SAN or iSCSI configuration. Database files and transaction log files located on a remote network directory can lead to poor performance, data corruption, and server instability.

    For more information, see [external link] http://www.sybase.com/detail?id=1034790.

    For best results, the transaction log should be kept on a different disk from the database files. See The transaction log.

  • Database options   For each database file you start, you can provide database options that control certain aspects of its behavior. See The SQL Anywhere database server.

Case sensitivity

Database and server options are generally case sensitive. You should enter all options in lowercase.

Listing available options

To list the database server options

  • Run the following command:

dbeng11 -?

Logging database server actions
Suppressing Windows event log messages