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 dialog appears, allowing you to Browse to your database file.
The elements of the database server command include the following:
Executable This can be either the personal server or the network server.
For more information about the executable names on different operating systems, see Introduction to running SQL Anywhere database servers.
In this chapter, unless discussing network-specific options, the personal server is used in sample commands. The network server takes a very similar set of options.
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 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.
In examples throughout this chapter where there are several options, they appear on separate lines for clarity, as they could be written in a configuration file. If you enter them directly at the command prompt, you must enter them all on one line.
Database and server options are generally case sensitive. You should enter all options in lowercase.
Open a command prompt.
Enter the following command:
dbeng10 -?