Deploying database servers

You can deploy a database server by making the SQL Anywhere installer available to your end users. By selecting the proper option, each end user is guaranteed of getting the files they need.

The simplest way to deploy a personal database server or a network database server is to use the Deployment Wizard. For more information, see Using the Deployment Wizard.

To run a database server, you need to install a set of files. The files are listed in the following table. All redistribution of these files is governed by the terms of your license agreement. You must confirm whether you have the right to redistribute the database server files before doing so.

Windows	Linux / Unix	Mac OS X
dbeng12.exe	dbeng12	dbeng12
dbeng12.lic	dbeng12.lic	dbeng12.lic
dbsrv12.exe	dbsrv12	dbsrv12
dbsrv12.lic	dbsrv12.lic	dbsrv12.lic
dbserv12.dll	libdbserv12_r.so, libdbtasks12_r.so	libdbserv12_r.dylib, libdbtasks12_r.dylib
dbscript12.dll	libdbscript12_r.so	libdbscript12_r.dylib
dblg[LL]12.dll	dblg[LL]12.res	dblgen12.res
dbghelp.dll	N/A	N/A
dbctrs12.dll	N/A	N/A
dbextf.dll¹	libdbextf.so¹	libdbextf.dylib¹
dbicu12.dll²	libdbicu12_r.so²	libdbicu12_r.dylib²
dbicudt12.dll^{2, 3}	libdbicudt12.so²	libdbicudt12.dylib²
sqlany.cvf	sqlany.cvf	sqlany.cvf
dbrsakp12.dll⁴	libdbrsakp12_r.so⁴	libdbrsakp12_r.dylib⁴
dbodbc12.dll⁵	libdbodbc12.so⁵	libdbodbc12.dylib⁵
N/A	libdbodbc12_n.so⁵	libdbodbc12_n.dylib⁵
N/A	libdbodbc12_r.so⁵	libdbodbc12_r.dylib⁵
dbjdbc12.dll⁵	libdbjdbc12.so⁵	libdbjdbc12.dylib⁵
java\jconn3.jar⁵	java/jconn3.jar⁵	java/jconn3.jar⁵
java\sajdbc.jar^{5, 9}	java/sajdbc.jar^{5, 9}	java/sajdbc.jar^{5, 9}
java\sajdbc4.jar⁵	java/sajdbc4.jar⁵	java/sajdbc4.jar⁵
java\sajvm.jar⁵	java/sajvm.jar⁵	java/sajvm.jar⁵
java\cis.zip⁶	java/cis.zip⁶	java/cis.zip⁶
dbcis12.dll⁷	libdbcis12.so⁷	libdbcis12.dylib⁷
libsybbr.dll⁸	libsybbr.so⁸	libsybbr.dylib⁸

¹ Required only if using system extended stored procedures and functions (xp_*).

² Required only if the database character set is multi-byte or if the UCA collation sequence is used.

³ On Windows Mobile, the file name to deploy is called dbicudt12.dat.

⁴ Required only for encrypted TDS connections.

⁵ Required only if using Java in the database.

⁶ Required only if using Java in the database and remote data access.

⁷ Required only if using remote data access.

⁸ Required only for archive backups.

⁹ Required only for JDBC 3.0.

Notes

Depending on your situation, you should choose whether to deploy the personal database server (dbeng12) or the network database server (dbsrv12).
You must include the separate corresponding license file (dbeng12.lic or dbsrv12.lic) when deploying a database server. The license files are located in the same directory as the server executables.
A language resource library file should also be included. The table above show files with the designation [LL]. There are several message files each supporting a different language. If you want to install support for different languages, you have to include the resource files for these languages. Replace [LL] with the language code (for example, en, de, jp, etc.).
The Java VM jar file (sajvm.jar) is required only if the database server is to use the Java in the Database functionality.
The table does not include files needed to run utilities such as dbbackup.

For information about deploying utilities, see Deploying administration tools.
The database server xd option is useful in deployed applications since it prevents the database server from becoming the default database server. Connections are accepted only when the server name is included in the connection string.

For information about the xd option, see -xd dbeng12/dbsrv12 server option.

For information about specifying the server name, see ServerName (Server) connection parameter.

Windows Registry entries

To improve robustness across power failures on systems using certain Intel storage drivers, specific registry entries must be set. To determine if this step is required, first check that the parent key exists and then add a parameter value to the key (the steps are described below). Failure to set this parameter can result in lost data and corrupted databases in the event of a power failure.

To improve robustness on Intel storage drivers

Check that the following registry entry exists.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iastor\Parameters\

If it does then add a REG_DWORD value named EnableFlush within this key and assign it the data value 1. Here is a sample registry change file.

REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iastor\Parameters]
"EnableFlush"=dword:00000001

Check that the following registry entry exists.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iastorv\Parameters\

If it does then add a REG_DWORD value named EnableFlush within this key and assign it the data value 1. Here is a sample registry change file.

REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iastorv\Parameters]
"EnableFlush"=dword:00000001

To ensure that messages written by the server to the Event Log on Windows are formatted correctly, you must create a registry key.

To format Event Log messages properly

Create the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SQLANY 12.0

Within this key, add a REG_SZ value named EventMessageFile and assign it the data value of the fully qualified location of dblgen12.dll, for example, C:\Program Files\SQL Anywhere 12\Bin32\dblgen12.dll. The English language DLL, dblgen12.dll, can be specified regardless of the deployment language. Here is a sample registry change file.

REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SQLANY 12.0]
"EventMessageFile"="c:\\sa12\\bin32\\dblgen12.dll"

For the 64-bit version of the server, the registry key is SQLANY64 12.0.

To ensure that messages written by MESSAGE ... TO EVENT LOG statements to the Event Log on Windows are formatted correctly, create the following registry key.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SQLANY 12.0 Admin

Within this key, add a REG_SZ value named EventMessageFile and assign it the data value of the fully qualified location of dblgen12.dll, for example, C:\Program Files\SQL Anywhere 12\Bin32\dblgen12.dll. The English language DLL, dblgen12.dll, can be specified regardless of the deployment language. Here is a sample registry change file.

REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SQLANY 12.0 Admin]
"EventMessageFile"="c:\\sa12\\bin32\\dblgen12.dll"

For the 64-bit version of the server, the registry key is SQLANY64 12.0 Admin.

You can suppress Windows event log entries by setting up a registry key. The registry key is:

Software\Sybase\SQL Anywhere\12.0\EventLogMask

and it can be placed in either the HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE hive. To control event log entries, create a REG_DWORD value named EventLogMask and assign it a bit mask containing the internal bit values for the different Windows event types. The three types supported by the SQL Anywhere database server are:

EVENTLOG_ERROR_TYPE        0x0001
EVENTLOG_WARNING_TYPE      0x0002
EVENTLOG_INFORMATION_TYPE  0x0004

For example, if the EventLogMask key is set to zero, no messages appear at all. A better setting would be 1, so that informational and warning messages don't appear, but errors do. The default setting (no entry present) is for all message types to appear. Here is a sample registry change file.

REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\SQL Anywhere\12.0]
"EventLogMask"=dword:00000007

Registering DLLs on Windows
Mac OS X considerations
Deploying databases

Discuss this page in DocCommentXchange.