File naming conventions

SQL Anywhere uses consistent file naming conventions to help identify and group system components.

These conventions include:

  • Version number   The SQL Anywhere version number is indicated in the file name of the main server components (executable files, dynamic link libraries, shared objects, license files, and so on).

    For example, the file dbeng11.exe is a version 11 executable for Windows.

  • Language   The language used in a language resource library is indicated by a two-letter code within its file name. The two characters before the version number indicate the language used in the library. For example, dblgen11.dll is the message resource library for the English language. These two-letter codes are specified by ISO standard 639.

    For more information about language labels, see Language Selection utility (dblang).

    For a list of the languages available in SQL Anywhere, see Localized versions of SQL Anywhere.

Identifying other file types

The following table identifies the platform and function of SQL Anywhere files according to their file extension. SQL Anywhere follows standard file extension conventions where possible.

File extension Platform File type
.bat, .cmd Windows Batch command files
.chm, .chw Windows Help system file
.dll Windows Dynamic Link Library
.exe Windows Executable file
.ini All Initialization file
.lic All License file
.lib Varies by development tool Static runtime libraries for the creation of embedded SQL executables
.res Linux/Unix, Mac OS X Language resource file for non-Windows environments
.so Linux/Unix Shared object or shared library file. The equivalent of a Windows DLL
.bundle, .dylib Mac OS X Shared object file. The equivalent of a Windows DLL
Database file names

SQL Anywhere databases are composed of two elements:

  • Database file   This is used to store information in an organized format. By default, this file uses a .db file extension. There may also be additional dbspace files. These files could have any file extension including none.

  • Transaction log file   This is used to record all changes made to data stored in the database file. By default, this file uses a .log file extension, and is generated by SQL Anywhere if no such file exists and a log file is specified to be used. A mirrored transaction log has the default extension of .mlg.

These files are updated, maintained and managed by the SQL Anywhere relational database management system.