dialects. 8.4. DB Gateway 42 Apache ShardingSphere document 8.4.6 Limitations The SQL dialect translation of Apache ShardingSphere is experimental. Currently, only MySQL/PostgreSQL dialects can be automatically recommend enabling it only if the following conditions are met: ‐ Pure OLTP scenarios. ‐ The CPU of the machine which deployed the ShardingSphere process has reached the bottleneck. ‐ Most of the CPUs are used shardingsphere:shardingsphere-standalone-mode-core, the persis‐ tence definition core of single‐machine mode configuration information • org.apache.shardingsphere:shardingsphere-standalone-mode-repository-jdbc-h2

dialects. 8.4. DB Gateway 42 Apache ShardingSphere document 8.4.6 Limitations The SQL dialect translation of Apache ShardingSphere is experimental. Currently, only MySQL/PostgreSQL dialects can be automatically recommend enabling it only if the following conditions are met: ‐ Pure OLTP scenarios. ‐ The CPU of the machine which deployed the ShardingSphere process has reached the bottleneck. ‐ Most of the CPUs are used recommend enabling it only if the following conditions are met: ‐ Pure OLTP scenarios. ‐ The CPU of the machine which deployed the ShardingSphere process has reached the bottleneck. ‐ Most of the CPUs are used

Different database projects may have different SQL dialects. 3.5.6 Limitations The SQL dialect translation of Apache ShardingSphere is experimental. Currently, only MySQL/PostgreSQL dialects can be automatically shardingsphere:shardingsphere-standalone-mode-core, the persis‐ tence definition core of single‐machine mode configuration information • org.apache.shardingsphere:shardingsphere-standalone-mode-repository-jdbc-h2 D a t a T y p e * Description Def ault Va lue worker‐id (?) l o n g The unique ID for working machine 0 max ‐tolerate‐time‐diff erence‐milliseconds (?) l o n g The max tolerate time for different

Different database projects may have different SQL dialects. 3.5.6 Limitations The SQL dialect translation of Apache ShardingSphere is experimental. Currently, only MySQL/PostgreSQL dialects can be automatically D a t a T y p e * Description Def ault Va lue worker‐id (?) l o n g The unique ID for working machine 0 max ‐tolerate‐time‐diff erence‐milliseconds (?) l o n g The max tolerate time for different SQL translation continues on next page 4.4. Error Code 290 Apache ShardingSphere document, v5.2.0 Table 1 – continued from previous page SQL State Vendor Code Reason 42000 11201 Translation error

threads for 30 minutes, and one MySQL has been deployed on one machine, while the scenario of MySQL used for comparison is deployed on one machine with one instance. Test Scenarios Single Route On the basis basis of one thousand data volume, four databases that are deployed on the same machine and each contains 1024 tables with id used for database sharding and k used for table sharding are designed for The following tasks are run on a separate Sysbench pressure generating machine via Jenkins slave: (runs on the {host-sysbench} machine) 2. sysbench_sharding: a. Sharding scenarios for remote deployment

D a t a T y p e * Description Def ault Va lue worker‐id (?) l o n g The unique ID for working machine 0 max ‐tolerate‐time‐diff erence‐milliseconds (?) l o n g The max tolerate time for different threads for 30 minutes, and one MySQL has been deployed on one machine, while the sce‐ nario of MySQL used for comparison is deployed on one machine with one instance. Test Scenarios Single Route On the the basis of one thousand data volume, four databases that are deployed on the same machine and each contains 1024 tables with id used for database sharding and k used for table sharding are designed for

threads for 30 minutes, and one MySQL has been deployed on one machine, while the sce‐ nario of MySQL used for comparison is deployed on one machine with one instance. Test Scenarios Single Route On the the basis of one thousand data volume, four databases that are deployed on the same machine and each contains 1024 tables with id used for database sharding and k used for table sharding are designed for The following tasks are run on a separate Sysbench pressure generating machine via Jenkins slave: (runs on the {host-sysbench} machine) 2. sysbench_sharding: a. Sharding scenarios for remote deployment

threads for 30 minutes, and one MySQL has been deployed on one machine, while the sce‐ nario of MySQL used for comparison is deployed on one machine with one instance. 7.7. Test 313 Apache ShardingSphere Single Route On the basis of one thousand data volume, four databases that are deployed on the same machine and each contains 1024 tables with id used for database sharding and k used for table sharding are The following tasks are run on a separate Sysbench pressure generating machine via Jenkins slave: (runs on the {host-sysbench} machine) 2. sysbench_sharding: a. Sharding scenarios for remote deployment

File access failed, reason is: %s 42000 11200 Can not support database ‘%s‘ in SQL translation 42000 11201 Translation error, SQL is: %s 25000 11320 Switch transaction type failed, please terminate the

方言转换 SQL State Vendor Code 错误信息 42000 20440 Can not support database ‘%s‘ in SQL translation. 42000 20441 Translation error, SQL is: %s 流量治理 SQL State Vendor Code 错误信息 42S02 20500 Can not get traffic