You can use either Firebird or Microsoft SQL Server as the back-end database. The following table can help you decide on what database to use.
Firebird | Microsoft SQL Server | |
|---|---|---|
Server installation | Must be installed on the same server as MVE. | Can be run from any server. |
Communication | Locked down to only localhost. | Communicates over a static port or a dynamic named instance. SSL/TLS communication with a secured Microsoft SQL server is supported. |
Performance | Shows performance issues with large fleets. | Shows the best performance for large fleets. |
Database size | Default database sizes are 6MB for FRAMEWORK, and 1MB for MONITOR and QUARTZ. The FRAMEWORK table grows at 1KB for each printer record that is added. | Default database sizes are 20MB for FRAMEWORK, and 4.5MB for MONITOR and QUARTZ. The FRAMEWORK table grows at 1KB for each printer record that is added. |
Configuration | Configured automatically during installation. | Requires preinstallation setup. |
If you are using Firebird, then the MVE installer installs and configures Firebird with no other configuration required.
If you are using Microsoft SQL Server, then before installing MVE, do the following:
Allow the application to run automatically.
Set the network libraries to use TCP/IP sockets.
Create the following databases:
FRAMEWORK
MONITOR
QUARTZ
If you are using a named instance, then set the Microsoft SQL Server Browser service to start automatically. Otherwise, set a static port on the TCP/IP sockets.
Create a user account with dbowner rights to all three databases that MVE uses to connect to and set up the database. If the user is a Microsoft SQL Server account, then enable the Microsoft SQL Server and the Windows Authentication modes on the Microsoft SQL Server.
Assign the dbo rights to the database user, and then set the dbo schema as the default schema.