diff options
| author | MikeBirnstiehl <michael.birnstiehl@sonarsource.com> | 2019-04-18 08:49:34 +0200 |
|---|---|---|
| committer | sonartech <sonartech@sonarsource.com> | 2019-04-23 10:37:57 +0200 |
| commit | b988394a088640add8c2b04887ec03b2aa8b6515 (patch) | |
| tree | c8d6c62baa46fa803b813be701933864a066b7b8 /server/sonar-docs | |
| parent | ee9a724c1b7772c419fbd009a0bd58c1d3234bdc (diff) | |
| download | sonarqube-b988394a088640add8c2b04887ec03b2aa8b6515.tar.gz sonarqube-b988394a088640add8c2b04887ec03b2aa8b6515.zip | |
DOCS remove MySQL support add migrator info
Diffstat (limited to 'server/sonar-docs')
5 files changed, 22 insertions, 24 deletions
diff --git a/server/sonar-docs/src/pages/instance-administration/system-info.md b/server/sonar-docs/src/pages/instance-administration/system-info.md index e9f379b3c9b..c97287949e9 100644 --- a/server/sonar-docs/src/pages/instance-administration/system-info.md +++ b/server/sonar-docs/src/pages/instance-administration/system-info.md @@ -66,6 +66,9 @@ The best approach there is to query the database. The actual query varies based [[collapse]] | ## MySQL +| +|**Note** – Starting with version 7.9, SonarQube will no longer support MySQL. To migrate from MySQL to a supported database, see the [MySQL Migrator tool](https://github.com/SonarSource/mysql-migrator). +| | Global LOCs | ``` | select sum(pm.value) as global_loc from projects p @@ -226,6 +229,9 @@ The best approach there is to query the database. The actual query varies based **SonarQube 6.0-6.6** [[collapse]] | ## MySQL +| +|**Note** – Starting with version 7.9, SonarQube will no longer support MySQL. To migrate from MySQL to a supported database, see the [MySQL Migrator tool](https://github.com/SonarSource/mysql-migrator). +| | Global LOCs | ``` | select sum(pm.value) as global_loc from projects p diff --git a/server/sonar-docs/src/pages/requirements/requirements.md b/server/sonar-docs/src/pages/requirements/requirements.md index c56776eb2dc..d015e5b647f 100644 --- a/server/sonar-docs/src/pages/requirements/requirements.md +++ b/server/sonar-docs/src/pages/requirements/requirements.md @@ -50,19 +50,13 @@ We recommend using the Critical Path Update (CPU) releases. | |  Collation must be case-sensitive (CS) and accent-sensitive (AS) (example: Latin1_General_CS_AS) | | |  READ_COMMITTED_SNAPSHOT must be set on the SonarQube database to avoid potential deadlocks under heavy load | | |  Both Windows authentication (“Integrated Security”) and SQL Server authentication are supported. See the Microsoft SQL Server section in Installing/installation/installing-the-server page for instructions on configuring authentication. | -| [Oracle] (http://www.oracle.com/database/) |  10G | +| [Oracle](http://www.oracle.com/database/) |  10G | | |  11G with backward-compatible [Oracle 12.2.x](http://www.oracle.com/technetwork/database/features/jdbc/jdbc-ucp-122-3110062.html) drivers | | |  12C with [Oracle 12.2.x](http://www.oracle.com/technetwork/database/features/jdbc/jdbc-ucp-122-3110062.html) drivers | | |  XE Editions are supported | |  Must be configured to use a UTF8-family charset (see NLS_CHARACTERSET) | | |  The driver ojdbc14.jar is not supported | | |  Only the thin mode is supported, not OCI | -| [MySQL](http://www.mysql.com/) | Not recommended for large instances | -| |  5.6 | -| |  5.7 | -| |  Must be configured to use UTF8 charset and a case-sensitive (CS) collation | -| |  Only InnoDB storage engine is supported, but not MyISAM | -| | Only the bundled mysql-connector-java jar is supported | ### Web Browser To get the full experience SonarQube has to offer, you must enable JavaScript in your browser. diff --git a/server/sonar-docs/src/pages/setup/install-server.md b/server/sonar-docs/src/pages/setup/install-server.md index ee7f185c6b6..8089274d531 100644 --- a/server/sonar-docs/src/pages/setup/install-server.md +++ b/server/sonar-docs/src/pages/setup/install-server.md @@ -59,15 +59,6 @@ If you want to use a custom schema and not the default "public" one, the Postgre ALTER USER mySonarUser SET search_path to mySonarQubeSchema ``` -### MySQL (not recommended) - -[[warning]] -| MySQL is not supported for [Data Center Edition](https://www.sonarsource.com/plans-and-pricing/data-center/). - -There are two well-known engines that can be used in MySQL: MyISAM and InnoDB. MyISAM is the oldest of the two engines and is being progressively replaced by InnoDB. InnoDB is clearly faster and scales better with SonarQube as the number of projects under quality control increases. If you were an early adopter of SonarQube, you probably have a series of tables that are still using MyISAM. To improve performance, you should change the engine for all tables to InnoDB. - -Once all SonarQube tables are using the InnoDB engine, the first thing to do is allocate a maximum amount of RAM to your MySQL instance with the `innodb_buffer_pool_size` parameter and give at least 15Mb to the `query_cache_size` parameter. Read this article about [InnoDB Performance Optimization Basics](https://www.percona.com/blog/2007/11/01/innodb-performance-optimization-basics/) for more information. - ## Installing the Web Server First, check the [requirements](/requirements/requirements/). Then download and unzip the [distribution](http://www.sonarqube.org/downloads/) (do not unzip into a directory starting with a digit). diff --git a/server/sonar-docs/src/pages/setup/upgrade-notes.md b/server/sonar-docs/src/pages/setup/upgrade-notes.md index 35ff9fcc302..b1052a43c2d 100644 --- a/server/sonar-docs/src/pages/setup/upgrade-notes.md +++ b/server/sonar-docs/src/pages/setup/upgrade-notes.md @@ -16,6 +16,9 @@ Only the following scanner versions are compatible with SonarQube 7.8: * SonarQube Scanner Maven 3.3.0.603+ * SonarQube Scanner Gradle 2.3+ +**MySQL Deprecation and Migration** +This is the last version that will support MySQL. To migrate from MySQL to a supported database, see the [MySQL Migrator tool](https://github.com/SonarSource/mysql-migrator). + **Notifications changes** The notifications algorithm has been replaced with one that offers better performance during background task processing. Additionally, issue change notifications spawned analysis or bulk change now generate only one email per event rather than one email per issue. diff --git a/server/sonar-docs/src/pages/setup/upgrading.md b/server/sonar-docs/src/pages/setup/upgrading.md index 51c0766ac96..fef6fac162b 100644 --- a/server/sonar-docs/src/pages/setup/upgrading.md +++ b/server/sonar-docs/src/pages/setup/upgrading.md @@ -4,19 +4,20 @@ url: /setup/upgrading/ --- <!-- sonarqube --> -Upgrading across multiple, non-LTS versions is handled automatically. However, if in your migration path you have an LTS version, you must first migrate to this LTS and then migrate to your target version. +Upgrading across multiple, non-LTS versions is handled automatically. However, if you have an LTS version in your migration path, you must first migrate to this LTS and then migrate to your target version. Example 1 : 5.1 -> 7.0, migration path is 5.1 -> 5.6.7 LTS -> 6.7.x LTS -> 7.0 Example 2 : 6.2 -> 6.7, migration path is 6.2 -> 6.7.x LTS (where x is the latest patch available for 6.7 - you don't need to install all the intermediary patches, just take the latest) -## How to Upgrade? +## Upgrade Guide -This is a generic upgrade guide, please read carefully the Upgrade Notes of your target version and of each intermediate version, if any (below). +This is a generic upgrade guide. Carefully read the [Release Upgrade Notes](/setup/upgrade-notes/) of your target version and of any intermediate version(s). - Planning to Upgrade to a Commercial Editions? -If you are targetting to move to 6.7 LTS and to install a commercial Edition, please read this [documentation](https://docs.sonarqube.org/display/SONARQUBE67/SonarSource+Editions). + **Planning to Upgrade to a Commercial Edition?** +If you are moving to 6.7 LTS and installing a Commercial Edition, please read this [documentation](https://docs.sonarqube.org/display/SONARQUBE67/SonarSource+Editions). -Before you start, backup your SonarQube Database. Upgrade problems are rare, but you'll want the backup if anything does happen. +[[warning]] +|  Before you start, back up your SonarQube Database. Upgrade problems are rare, but you'll want the backup if anything does happen. 1. Download and unzip the SonarQube distribution of your edition in a fresh directory, let's say `$NEW_SONARQUBE_HOME` 2. Manually install the non-default plugins that are compatible with your version of SonarQube. Use the [Compatibility Matrix](https://docs.sonarqube.org/display/PLUG/Plugin+Version+Matrix) to ensure that the versions you install are compatible with your server version. Note that the most recent versions of all SonarSource code analyzers available in your edition are installed by default. Simply copying plugins from the old server to the new is not recommended; incompatible or duplicate plugins could cause startup errors. @@ -27,11 +28,14 @@ If you are using the Oracle DB, copy its JDBC driver into `$NEW_SONARQUBE_HOME/e 6. Browse to `http://yourSonarQubeServerURL/setup` and follow the setup instructions 7. Reanalyze your projects to get fresh data -## Anything Else? +## Additional Information + +### MySQL Deprecation and Migration +Starting with version 7.9, SonarQube will no longer support MySQL. To migrate from MySQL to a supported database, see the [MySQL Migrator tool](https://github.com/SonarSource/mysql-migrator). ### Oracle Clean-up -Starting with 6.6, there's an additional step you may want to perform if you're using Oracle. On Oracle the database columns to be dropped are now marked as UNUSED and are not physically dropped anymore. To reclaim disk space, Oracle administrators must drop these unused columns manually. The SQL request is `ALTER TABLE foo DROP UNUSED COLUMNS`. The relevant tables are listed in the system table `all_unused_col_tabs`. +Starting with version 6.6, there's an additional step you may want to perform if you're using Oracle. On Oracle, the database columns to be dropped are now marked as UNUSED and are not physically dropped anymore. To reclaim disk space, Oracle administrators must drop these unused columns manually. The SQL request is `ALTER TABLE foo DROP UNUSED COLUMNS`. The relevant tables are listed in the system table `all_unused_col_tabs`. ### Additional Database Maintenance |