Database server deployment

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 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
dbeng16.exe	dbeng16	dbeng16
dbeng16.lic	dbeng16.lic	dbeng16.lic
dbsrv16.exe	dbsrv16	dbsrv16
dbsrv16.lic	dbsrv16.lic	dbsrv16.lic
dbserv16.dll	libdbserv16_r.so, libdbtasks16_r.so	libdbserv16_r.dylib, libdbtasks16_r.dylib
dbscript16.dll	libdbscript16_r.so	libdbscript16_r.dylib
dblg[LL]16.dll	dblg[LL]16.res	dblgen16.res
dbghelp.dll	N/A	N/A
dbctrs16.dll	N/A	N/A
dbextf.dll¹	libdbextf.so¹	libdbextf.dylib¹
dbicu16.dll²	libdbicu16_r.so²	libdbicu16_r.dylib²
dbicudt16.dll^{2, 3}	libdbicudt16.so²	libdbicudt16.dylib²
sqlany.cvf	sqlany.cvf	sqlany.cvf
dbrsakp16.dll⁴	libdbrsakp16_r.so⁴	libdbrsakp16_r.dylib⁴
dbodbc16.dll⁵	libdbodbc16.so⁵	libdbodbc16.dylib⁵
dbjodbc16.dll⁵	libdbjodbc16.so⁵	libdbjodbc16.dylib⁵
N/A	libdbodbc16_n.so⁵	libdbodbc16_n.dylib⁵
N/A	libdbodbc16_r.so⁵	libdbodbc16_r.dylib⁵
dbjdbc16.dll⁶	libdbjdbc16.so⁶	libdbjdbc16.dylib⁶
java\sajdbc4.jar⁶	java/sajdbc4.jar⁶	java/sajdbc4.jar⁶
java\sajvm.jar⁶	java/sajvm.jar⁶	java/sajvm.jar⁶
dbcis16.dll⁷	libdbcis16.so⁷	libdbcis16.dylib⁷
libsybbr.dll⁸	libsybbr.so⁸	libsybbr.dylib⁸

¹ Required only if using the deprecated version of the system extended stored procedures and functions (xp_*). The use_old_dbextf.sql script must be used for databases that want to use the deprecated version.

² 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 dbicudt16.dat.

⁴ Required only for encrypted TDS connections.

⁵ Required only if using Java in the database with version 10 databases.

⁶ Required only if using Java in the database.

⁷ Required only if using remote data access.

⁸ Required only for archive backups.

Notes

Depending on your situation, you should choose whether to deploy the personal database server (dbeng16) or the network database server (dbsrv16).
You must include the separate corresponding license file (dbeng16.lic or dbsrv16.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 shows files with the designation [LL]. There are several message files each supporting a different language. 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, and so on).
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 Administration tool deployment.
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 database server option.

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

Improving robustness on Intel storage drivers
Formatting Event Log messages
Mac OS X considerations
Database deployment

Discuss this page in DocCommentXchange.