Mimer SQL for Windows exists in both 32-bit and 64-bit versions. Each version is packaged separately. Please make sure you use a matching version when installing.
64-bit implementation specifics
The 64-bit implementation supports both 32-bit and 64-bit clients. The directory structure of a default installation looks as follows:
| Directory | Description |
|---|---|
| C:\Program Files\Mimer SQL 10.1 | This directory contains the 64-bit runtime libraries and executables. 64-bit applications reference the dynamic link libraries stored in this directory. |
| C:\Program Files (x86)\Mimer SQL 10.1 32-Bit | This directory contains 32-bit runtime libraries. 32-bit appThis directory contains 32-bit runtime libraries. 32-bit applications reference the dynamic link libraries stored in this directory. |
The actual names C:\Program Files and C:\Program Files (x86) may be different depending on installation language for the computer.
Scope of Database names
Database names are stored under the 64-bit registry. Both 32-bit and 64-bit applications automatically reference the correct registry locations. Only one set of database names are maintained.
Scope of ODBC data source names
ODBC data source names are stored separately for 64-bit and 32-bit applications. The data sources must be set up separately for each environment using different ODBC Administrators. These can be reached from the Mimer SQL program menu using the shortcuts "ODBC 64-bit Administrator" and "ODBC 32-bit Administrator".
The 64-bit ODBC Data Sources can also be maintained using the Mimer Administrator by choosing either of the tabs User DSN or System DSN.
Large page memory region
The 64-bit implementation supports the use of a large page memory region for the bufferpool. This means that the memory is allocated consecutively in physical memory. The memory is not paged and cannot therefore be used for anything else as long as the database server is running. In addition, the allocation may fail with the error message "VirtualAlloc: insufficient system resources exists to complete the requested service" if the memory is fragmented. The benefit is that no paging file is used and that memory accesses are very efficient.
64-bit implementation limits
The 64-bit implementation of Mimer SQL on Windows currently supports SQL-Pools and Bufferpools each with a size of up to 16 GB. The actual sizes used are set in the Mimer Administrator under the tab Memory for a local database definition.