2021.2

Database Considerations
This page describes the different considerations and pre-requisites for the database back-end
used by PlanetPress Connect, whether using the MySQL instance provided by the installer, or
pre-existing (external) instance.
Using the MySQL Instance from the Installer
The MySQL Instance provided in the "Installation Wizard" on page38is already pre-configured
with options to provide the most stable back-end setup.
These are the specific options that have been changed in our version of "my.ini":
l max_connections = 200 : PlanetPress Connect uses a lot of database connections. This
number ensures that even in high volume environments, enough connections will be
available.
l max_allowed_packet = 500M : In some implementations, especially when using Capture
OnTheGo, large packet sizes are required to allow transferring binary files. This
substantial packet size maximum setting ensures that the data received by PlanetPress
Connect will be able to be stored within the database.
l character-set-server = utf8 , collation-server = utf8_unicode_ci , default-character-
set=utf8 : These indicate database support for UTF-8/Unicode.
Installing / Updating Connect using an existing MySQL instance
If MySQL Server is already present and you wish to use it, the following should be taken into
consideration:
l The minimum supported MySQL version is MySQL5.6.
l The MySQL account must have access to all permissions using the GRANT Command,
including creating databases.
l The database configuration must include the options detailed in the "Using the MySQL
Instance from the Installer" above topic.
l The database configuration must allow the use of mixed case table names.
This is particularly an issue on Linux MySQLinstallations.
l The SQL instance must be open to access from other computers. This means the bind-
address option should not be set to 127.0.0.1 or localhost.
Page 18