2019.1

l Regular database maintenance is required, such as database compacting, is
required by a system administrator.
l It is recommended to create an IT process that backs up the database regularly.
l The recommended ideal setup is a dedicated SQL Server PC, accessed by
PlanetPress Workflow through an ODBC connection on the local network.
l
Microsoft Access
l Database file (mdb) must be local to the PlanetPress Workflow computer. It cannot
be located on a network drive or another server.
l Total database size is limited to 4GB of data.
l Total size of a single table is 2GB.
l May be unstable in large implementations.
l
MySQL
l Database can be in any location, but performance will depend on the speed of the
connection between PlanetPress and the MySQL server.
l MySQL's performance has been slower than SQL Server and SQL Server Express
during our tests.
l By default, MySQL is configured not to allow any SQL request larger than 16 megs.
l In the event where 2 requests are made simultaneously on the same record, MySQL
will queue one of the requests and execute it once the first one is done. In extremely
rare cases this may cause a timeout on very large requests.
l
MSSQL (Microsoft SQL Server)
l All versions of the SQL Server are supported, including all Express versions.
l Database can be in any location, but performance will depend on the speed of the
connection between PlanetPress Production and the SQL server.
l In the event where 2 requests are made simultaneously on the same record, SQL
Server will drop the most complex request. Resubmitting the PGC for processing
should resolve this issue. This, however, should happen only rarely.
l When configuring the ODBC connection, your must use the Microsoft version of the
driver, and not the Native SQL version of the driver. This is due to a technical
limitation of the native driver that interferes with the PlanetPress Suite database
requests.
Specifically for PlanetPress Capture, these considerations mean the following:
Page 202