Difference between revisions of "Database"

From regify WIKI
Jump to navigation Jump to search
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
== supported database systems ==
+
== Supported Database Systems ==
The default database for a regify-provider system is '''MySQL''' in version 5.1 or greater. Alternatively, you can use '''ORACLE 10g to 11g''' database to run the regify-provider.
+
The default database for a regify-provider system is '''MariaDB'''. During installation of the regify software appliance, you are also able to select '''MySQL''' as an alternative.
  
== database structure ==
+
== Database Structure ==
  
The regify provider database consists of 15 tables, 34 indices (status May 2010). There are no stored procedures or views involved. In case of Oracle, nearly each table utilizes an additional sequence and trigger (for generating autoincrementing indexes).
+
The regify provider database consists of 49 tables, 95 indices (incl. PRIMARY keys, as of June 2019).
  
== needed space ==
+
== Needed Space ==
  
* 1 mio regify transactions need about 220 MB storage capacity.
+
* 1 mio regify transactions (regimail, regipay, regibill) need about 185 MB storage capacity.
 
* 1000 registered users need about 0,8 MB storage capacity.
 
* 1000 registered users need about 0,8 MB storage capacity.
  
As of theese small values, a capacity of 20GB will fit for about
+
As of those small values, a capacity of 20GB will fit for about
  
 
* 90 mio transactions
 
* 90 mio transactions
 
* 600'000 users
 
* 600'000 users
  
== amount of selects, inserts and updates ==
+
This number increases massively, if you plan to offer '''regichat''' and/or '''regibox'''. Please consider additional 5MB for each regibox user and 2MB for each regichat user.
 
 
Average portal visit:
 
* 19 selects
 
* 5 inserts
 
 
 
Sending and receiving one transaction:
 
* 13 selects
 
* 4 updates
 
* 4 inserts
 
 
 
Database-usage by repeating jobs:
 
* mailjob (every 5 minutes)
 
** 1 select
 
** 1 delete (only 1 delete per job. More traffic, if sending failed)
 
* daily
 
** 1 select per user
 
** 2 inserts per user
 
** 0,5 updates per user
 
** 0,2 deletes per user
 
 
 
The conrete values are depending on the number of failed invitings, non collected transactions and other circumstances.
 
 
 
== configuration details ==
 
 
 
=== MySQL ===
 
Initially, you don't need to care about any settings. At a later point, some optimisation may be needed.
 
 
 
=== Oracle ===
 
The needed charset for Oracle database usage is
 
 
 
NLS_CHARACTERSET: AL32UTF8
 
 
 
To allow lot's of users, please check the PROCESSES setting of your Orac le installation. In case this value is less than 200, please rise to a value of 300 to 1000 processes using
 
 
 
ALTER SYSTEM SET PROCESSES=300 SCOPE=SPFILE;
 

Revision as of 11:21, 19 August 2019

Supported Database Systems

The default database for a regify-provider system is MariaDB. During installation of the regify software appliance, you are also able to select MySQL as an alternative.

Database Structure

The regify provider database consists of 49 tables, 95 indices (incl. PRIMARY keys, as of June 2019).

Needed Space

  • 1 mio regify transactions (regimail, regipay, regibill) need about 185 MB storage capacity.
  • 1000 registered users need about 0,8 MB storage capacity.

As of those small values, a capacity of 20GB will fit for about

  • 90 mio transactions
  • 600'000 users

This number increases massively, if you plan to offer regichat and/or regibox. Please consider additional 5MB for each regibox user and 2MB for each regichat user.