Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 10.0.1 » SQL Anywhere Server - Database Administration » Connection Parameters and Network Protocol Options » Connection parameters

ConnectionName connection parameter [CON] Next Page

DatabaseFile connection parameter [DBF]

Indicates which database file you want to load and connect to when starting a database that is not already running.

If you want to connect to an already-running database, use the DatabaseName (DBN) parameter.


Embedded databases




There is no default setting.


The DatabaseFile (DBF) connection parameter is used to load and connect to a specific database file that is not already running on a database server.

You can also use UNC file names and Novell NetWare Directory Services file names.

For more information about using UNC file names and Novell NetWare Directory Services file names, see The SQL Anywhere database server.

It is recommended that deployed applications specify a database server name using the EngineName (ENG) parameter when attempting to autostart a database file if it is not already running. Otherwise, the application may connect to a different database server than intended. For example, the database server could connect to a different version of the SQL Anywhere server that is part of an embedded application and already running.


The database file must be on the same computer as the database server. Starting a database file that is located on a network drive can lead to file corruption.

See also

The DatabaseFile (DBF) connection parameter in the following example loads and connects to the sample database, demo.db:


For information about samples-dir, see Samples directory.

The following two examples assume that you have started a database file named cities.db, and renamed the database Kitchener as follows:

dbeng10 cities.db -n Kitchener

To successfully start and connect to a database and name it Kitchener:


Specifying DBF=cities.db would fail to connect to the running database named Kitchener.