Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
711:system_requirements_mysql [2024/08/29 14:19] – created - external edit 127.0.0.1711:system_requirements_mysql [2025/07/03 07:42] (current) – [Azure/AWS MySQL DB] Suess, Bernhard
Line 3: Line 3:
 ===== Native MySQL installation ===== ===== Native MySQL installation =====
  
-Stages supports MySQL 5.7 and 8.0 Community Editions.+Stages supports 8.0 Community Edition.
  
 The following settings are highly recommended: The following settings are highly recommended:
  
-<code>+<code ->
 character-set-server=utf8 character-set-server=utf8
 max_allowed_packet=500M max_allowed_packet=500M
Line 15: Line 15:
 sql-mode = "STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION" sql-mode = "STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION"
 default-time-zone="+00:00" default-time-zone="+00:00"
- 
 </code> </code>
  
 The following settings are recommended for MySQL 8.0, especially to improve database write performance: The following settings are recommended for MySQL 8.0, especially to improve database write performance:
  
-<code>+<code ->
 innodb_flush_log_at_trx_commit=2 innodb_flush_log_at_trx_commit=2
 sync_binlog=0 sync_binlog=0
Line 26: Line 25:
 </code> </code>
  
-Stages uses the INNODB engine. This can have impact on the server backup strategy, because INNODB files tend to become very large.+Stages use the INNODB engine. This can have impact on the server backup strategy, because INNODB files tend to become very large.
  
 If you run Stages with a MySQL database and have a virus scanner installed on the same server, please make sure that the virus scanner is not scanning the database directory as this might lead to database inconsistencies. This problem is a known MySQL error and Oracle is advising to proceed as described. If you run Stages with a MySQL database and have a virus scanner installed on the same server, please make sure that the virus scanner is not scanning the database directory as this might lead to database inconsistencies. This problem is a known MySQL error and Oracle is advising to proceed as described.
- 
-The Windows 7 search feature causes the same kind of problems as a virus scanner. Please disable this feature on the Stages server. 
  
  
Line 39: Line 36:
 In addition, the l''og_bin_trust_function_creators'' parameter of Azure MySQL DB must be set to 1. See [[https://stackoverflow.com/questions/11601692/mysql-amazon-rds-error-you-do-not-have-super-privileges|here for more info]]. In addition, the l''og_bin_trust_function_creators'' parameter of Azure MySQL DB must be set to 1. See [[https://stackoverflow.com/questions/11601692/mysql-amazon-rds-error-you-do-not-have-super-privileges|here for more info]].
  
-The connection timeout for Azure MySQL DB might be set very low. If you see connection errors after a while, you should set the connection timeout for Stages to 100 seconds via<code>+The connection timeout for Azure MySQL DB might be set very low. If you see connection errors after a while, you should set the connection timeout for Stages to 100 seconds via
  
 +<code ->
 torque.database.default.expiryTime=100000 torque.database.default.expiryTime=100000
- 
 </code> </code>
  
 in ''database.properties''. in ''database.properties''.
 +
 +
 ===== AWS RDS for MySQL ===== ===== AWS RDS for MySQL =====