Author: jstephens
Date: 2008-10-03 13:13:35 +0200 (Fri, 03 Oct 2008)
New Revision: 11963
Log:
Fix for Docs Bug #39836
(improve recommendation for calculating MaxNoOfAttributes)
(Thanks, Oli and JohanA!)
Modified:
trunk/refman-4.1/mysql-cluster-configuration.xml
trunk/refman-5.0/mysql-cluster-configuration.xml
trunk/refman-5.1/mysql-cluster-configuration.xml
Modified: trunk/refman-4.1/mysql-cluster-configuration.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster-configuration.xml 2008-10-03 11:02:18 UTC (rev 11962)
+++ trunk/refman-4.1/mysql-cluster-configuration.xml 2008-10-03 11:13:35 UTC (rev 11963)
Changed blocks: 1, Lines Added: 27, Lines Deleted: 12; 2778 bytes
@@ -2481,19 +2481,34 @@
TABLE</literal> statements that you might want to perform in
the future. This is due to the fact, during the execution of
<literal>ALTER TABLE</literal> on a Cluster table, 3 times
- the number of attributes as in the original table are used.
- For example, if a table requires 100 attributes, and you
- want to be able to alter it later, you need to set the value
- of <literal>MaxNoOfAttributes</literal> to 300. Assuming
- that you can create all desired tables without any problems,
- a good rule of thumb is to add two times the number of
- attributes in the largest table to
- <literal>MaxNoOfAttributes</literal> to be sure. You should
- also verify that this number is sufficient by trying an
- actual <literal>ALTER TABLE</literal> after configuring the
- parameter. If this is not successful, increase
+ the number of attributes as in the original table are used,
+ and a good practice is to allow double this amount. For
+ example, if the MySQL Cluster table having the greatest
+ number of attributes
+ (<replaceable>greatest_number_of_attributes</replaceable>)
+ has 100 attributes, a good starting point for the value of
+ <literal>MaxNoOfAttributes</literal> would be <literal>6 *
+ <replaceable>greatest_number_of_attributes</replaceable> =
+ 600</literal>.
+ </para>
+
+ <para>
+ You should also estimate the average number of attributes
+ per table and multiply this by the total number of MySQL
+ Cluster tables. If this value is larger than the value
+ obtained in the previous paragraph, you should use the
+ larger value instead.
+ </para>
+
+ <para>
+ Assuming that you can create all desired tables without any
+ problems, you should also verify that this number is
+ sufficient by trying an actual <literal>ALTER
+ TABLE</literal> after configuring the parameter. If this is
+ not successful, increase
<literal>MaxNoOfAttributes</literal> by another multiple of
- the original value and test it again.
+ <replaceable>greatest_number_of_attributes</replaceable> and
+ test it again.
</para>
</listitem>
Modified: trunk/refman-5.0/mysql-cluster-configuration.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster-configuration.xml 2008-10-03 11:02:18 UTC (rev 11962)
+++ trunk/refman-5.0/mysql-cluster-configuration.xml 2008-10-03 11:13:35 UTC (rev 11963)
Changed blocks: 1, Lines Added: 27, Lines Deleted: 12; 2778 bytes
@@ -2458,19 +2458,34 @@
TABLE</literal> statements that you might want to perform in
the future. This is due to the fact, during the execution of
<literal>ALTER TABLE</literal> on a Cluster table, 3 times
- the number of attributes as in the original table are used.
- For example, if a table requires 100 attributes, and you
- want to be able to alter it later, you need to set the value
- of <literal>MaxNoOfAttributes</literal> to 300. Assuming
- that you can create all desired tables without any problems,
- a good rule of thumb is to add two times the number of
- attributes in the largest table to
- <literal>MaxNoOfAttributes</literal> to be sure. You should
- also verify that this number is sufficient by trying an
- actual <literal>ALTER TABLE</literal> after configuring the
- parameter. If this is not successful, increase
+ the number of attributes as in the original table are used,
+ and a good practice is to allow double this amount. For
+ example, if the MySQL Cluster table having the greatest
+ number of attributes
+ (<replaceable>greatest_number_of_attributes</replaceable>)
+ has 100 attributes, a good starting point for the value of
+ <literal>MaxNoOfAttributes</literal> would be <literal>6 *
+ <replaceable>greatest_number_of_attributes</replaceable> =
+ 600</literal>.
+ </para>
+
+ <para>
+ You should also estimate the average number of attributes
+ per table and multiply this by the total number of MySQL
+ Cluster tables. If this value is larger than the value
+ obtained in the previous paragraph, you should use the
+ larger value instead.
+ </para>
+
+ <para>
+ Assuming that you can create all desired tables without any
+ problems, you should also verify that this number is
+ sufficient by trying an actual <literal>ALTER
+ TABLE</literal> after configuring the parameter. If this is
+ not successful, increase
<literal>MaxNoOfAttributes</literal> by another multiple of
- the original value and test it again.
+ <replaceable>greatest_number_of_attributes</replaceable> and
+ test it again.
</para>
</listitem>
Modified: trunk/refman-5.1/mysql-cluster-configuration.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-configuration.xml 2008-10-03 11:02:18 UTC (rev 11962)
+++ trunk/refman-5.1/mysql-cluster-configuration.xml 2008-10-03 11:13:35 UTC (rev 11963)
Changed blocks: 1, Lines Added: 27, Lines Deleted: 12; 2778 bytes
@@ -2589,19 +2589,34 @@
TABLE</literal> statements that you might want to perform in
the future. This is due to the fact, during the execution of
<literal>ALTER TABLE</literal> on a Cluster table, 3 times
- the number of attributes as in the original table are used.
- For example, if a table requires 100 attributes, and you
- want to be able to alter it later, you need to set the value
- of <literal>MaxNoOfAttributes</literal> to 300. Assuming
- that you can create all desired tables without any problems,
- a good rule of thumb is to add two times the number of
- attributes in the largest table to
- <literal>MaxNoOfAttributes</literal> to be sure. You should
- also verify that this number is sufficient by trying an
- actual <literal>ALTER TABLE</literal> after configuring the
- parameter. If this is not successful, increase
+ the number of attributes as in the original table are used,
+ and a good practice is to allow double this amount. For
+ example, if the MySQL Cluster table having the greatest
+ number of attributes
+ (<replaceable>greatest_number_of_attributes</replaceable>)
+ has 100 attributes, a good starting point for the value of
+ <literal>MaxNoOfAttributes</literal> would be <literal>6 *
+ <replaceable>greatest_number_of_attributes</replaceable> =
+ 600</literal>.
+ </para>
+
+ <para>
+ You should also estimate the average number of attributes
+ per table and multiply this by the total number of MySQL
+ Cluster tables. If this value is larger than the value
+ obtained in the previous paragraph, you should use the
+ larger value instead.
+ </para>
+
+ <para>
+ Assuming that you can create all desired tables without any
+ problems, you should also verify that this number is
+ sufficient by trying an actual <literal>ALTER
+ TABLE</literal> after configuring the parameter. If this is
+ not successful, increase
<literal>MaxNoOfAttributes</literal> by another multiple of
- the original value and test it again.
+ <replaceable>greatest_number_of_attributes</replaceable> and
+ test it again.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r11963 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 3 Oct |
