|
Section 1
Introduction
Section 2
Configuring for First Use
Section 3
Changing Admin Password
Section 4
Creating Accounts
Section 5
Global Component Settings
Section 6
Backups
Section 7
Log Files
Section 8
User Interface Settings
Section 9
Database Connections
9.2 Optimizing Hints
9.3 Connecting to a Different Database
9.4 Disabling and Enabling Internal
Database
9.5 Registering Database Plugin
9.6 Installing JDBC Drivers
Section 10
Non-Standard Ports
Section 11
Firewalls
Section 12
SSL
Section 13
Tracking and Recipient Profiles
Section 14
Editing INI Files
Section 15
Distributed Components
Section 16
User Interface Branding
Section 17
Evaluation Mode
Section 18
International Character Sets
Appendix A
Standard Default Ports
|
9.2 General Optimization Hints
The following
general information about how the Maestro User Interface uses
the database can help optimize the database installation for
use with the Maestro User Interface.
The
Maestro User Interface does not use large transactions. Any
transactions that are opened are then closed after a maximum
of a few hundred inserts or updates.
During
normal usage, the Maestro User Interface behaves with OLTP
(online transaction processing) characteristics. There is
a constant switch between read and write on the database.
However, if there are many reports running on the collected
tracking data, the characteristics of the Maestro User Interface’s
behavior shift more and more into OLAP (online analytical
processing), where the amount of (complex) reads outnumbers
the amount of writes.
Use
this information to optimize the database after analyzing
the usage of the Maestro User Interface to determine if it
is working more with OLTP or OLAP characteristics.
The database
that is used as storage for the Maestro User Interface should
be configured in a way that allows dynamic growth because
the data stored by the Maestro User Interface grows over time.
The growth rate corresponds to the number and the size of
the e-mail jobs that are delivered. Large e-mail jobs with
a high volume of collected tracking events will use more database
storage space than smaller e-mail jobs.
Some examples
of upper limits that might need to be adjusted for large volume
environments are:
- User space quota - Most databases limit the amount
of space that a given user may store in the database. This limit should
be set to "unlimited" or a sufficiently large value.
- Database
or tablespace size - Many database vendors, especially those
supporting larger database environments, support the sub-division of
the database server in smaller areas, sometimes called "tablespaces"
or a similar term (see the documentation for details). Normally, each
database account is assigned to one of these areas, which are then referred
to as "default tablespace" or "standard tablespace".
This part of the database should be configured in a way that it allows
dynamic growth, if possible. Note:
It is possible to use the Maestro User Interface with a database that
does not support this type of dynamic growth. To do so, an administrator
should make it part of the daily or weekly routine to check the amount
of space available for the Maestro User Interface.
- File
system size - Like other server applications storing persistent
data on the file system, the database storing the Maestro User Interface
data must reside on a server whose file system is monitored on a regular
basis, either through automated system administration tools or by an
administrator who regularly checks the system.
|