Versions Compared

Old Version 27

changes.mady.by.user Otto Šteinbaums

Saved on

compared with

New Version 28

changes.mady.by.user Otto Šteinbaums

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel

MySQL

You can create a separate flexbi_private user and grant it access to all MySQL databases which start with the flexbi_private prefix:

drfgrdgtdg

f

tgh

fthfthf 

(Replace secret with chosen password). When you will specify the database connection parameters in eazyBI then eazybi_private database will be created. Later when additional eazyBI accounts will be created then each account data will be stored in separate databases with names eazybi_jira_dwh_N where N is account ID number.

In addition you should download MySQL JDBC driver and copy included mysql-connector-java-*.jar to eazybi_private/lib directory (MySQL JDBC driver is not included in Private eazyBI distribution due to GPL license restrictions).

Please also tune MySQL memory settings to speed up both data import and data queries. The following my.cnf settings are recommended:

 

innodb_buffer_pool_size will specify how much database data MySQL can store in memory - adjust it to your available server memory (the more data MySQL will store in memory the less disk input/output operations will be performed). If you will change innodb_log_file_size then it will require that you delete existing MySQL log files before starting MySQL server.

Panel

PostgreSQL

You need to create a separate user flexbi_private with database creation rights for flex.bi:

Code Block
CREATE ROLE flexbi_private PASSWORD 'secret' LOGIN CREATEDB;

If you do not want to add the CREATEDB role to the flexbi_private user then manually create the flexbi_private database with flexbi_private user as the owner.

Each new flex.bi account will store data in a new flexbi_jira_dwh_N schema (where N is account ID number) in the same database.

Please tune PostgreSQL memory parameters. The following postgresql.conf settings are recommended:

Code Block
shared_buffers = 1024MB
wal_buffers = 32MB

The parameter shared_buffers will specify how much database data PostgreSQL can store in the memory - adjust it to your available server memory (the more data PostgreSQL will store in the memory the less disk input/output operations will be performed). The parameter wal_buffers affects the performance of writing transaction logs to disk.

...