Author: jstephens
Date: 2006-06-07 09:51:18 +0200 (Wed, 07 Jun 2006)
New Revision: 2294
Log:
NDB info regarding storage requirements (Stewart)
Also setting some repos ignore properties.
Modified:
trunk/refman-4.1/
trunk/refman-4.1/data-types.xml
trunk/refman-4.1/images/
trunk/refman-5.0/
trunk/refman-5.0/data-types.xml
trunk/refman-5.0/images/
trunk/refman-5.1/
trunk/refman-5.1/data-types.xml
trunk/refman-5.1/images/
Property changes on: trunk/refman-4.1
___________________________________________________________________
Name: svn:ignore
+ *.bak
Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml 2006-06-07 03:04:41 UTC (rev 2293)
+++ trunk/refman-4.1/data-types.xml 2006-06-07 07:51:18 UTC (rev 2294)
@@ -5095,6 +5095,11 @@
<literal>TEXT</literal> column accounts for only five to nine
bytes toward this size.
</para>
+
+ <indexterm>
+ <primary>MySQL Cluster</primary>
+ <secondary>storage requirements</secondary>
+ </indexterm>
<para>
<emphasis role="bold">Important</emphasis>: For tables using the
@@ -5113,7 +5118,26 @@
(<literal>INT</literal>) column types each require 4 bytes storage
per record.
</para>
-
+
+ <para>
+ In addition, when calculating storage requirements for Cluster
+ tables, you must remember that every table using the
+ <literal>NDBCluster</literal> storage engine requires a primary
+ key; if no primary key is defined by the user, then a
+ <quote>hidden</quote> primary key will be created by
+ <literal>NDB</literal>. This hidden primary key consumes 31-35
+ bytes per table record.
+ </para>
+
+ <para>
+ When calculating Cluster memory requirements, you may find useful
+ the <filename>ndb_size.pl</filename> utility which is available on
+ <ulink url="http://forge.mysql.com/">MySQLForge</ulink>. This
+ Perl script connects to a current MySQL (non-Cluster) database and
+ creates a report on how much space that database would require if
+ it used the <literal>NDBCluster</literal> storage engine.
+ </para>
+
<indexterm>
<primary>numeric types</primary>
</indexterm>
Property changes on: trunk/refman-4.1/images
___________________________________________________________________
Name: svn:ignore
+ *.bak
Property changes on: trunk/refman-5.0
___________________________________________________________________
Name: svn:ignore
+ *.bak
Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml 2006-06-07 03:04:41 UTC (rev 2293)
+++ trunk/refman-5.0/data-types.xml 2006-06-07 07:51:18 UTC (rev 2294)
@@ -4922,6 +4922,11 @@
<literal>TEXT</literal> column accounts for only five to nine
bytes toward this size.
</para>
+
+ <indexterm>
+ <primary>MySQL Cluster</primary>
+ <secondary>storage requirements</secondary>
+ </indexterm>
<para>
<emphasis role="bold">Important</emphasis>: For tables using the
@@ -4940,6 +4945,25 @@
(<literal>INT</literal>) column types each require 4 bytes storage
per record.
</para>
+
+ <para>
+ In addition, when calculating storage requirements for Cluster
+ tables, you must remember that every table using the
+ <literal>NDBCluster</literal> storage engine requires a primary
+ key; if no primary key is defined by the user, then a
+ <quote>hidden</quote> primary key will be created by
+ <literal>NDB</literal>. This hidden primary key consumes 31-35
+ bytes per table record.
+ </para>
+
+ <para>
+ When calculating Cluster memory requirements, you may find useful
+ the <filename>ndb_size.pl</filename> utility which is available on
+ <ulink url="http://forge.mysql.com/">MySQLForge</ulink>. This
+ Perl script connects to a current MySQL (non-Cluster) database and
+ creates a report on how much space that database would require if
+ it used the <literal>NDBCluster</literal> storage engine.
+ </para>
<indexterm>
<primary>numeric types</primary>
Property changes on: trunk/refman-5.0/images
___________________________________________________________________
Name: svn:ignore
+ *.bak
Property changes on: trunk/refman-5.1
___________________________________________________________________
Name: svn:ignore
+ *.bak
Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml 2006-06-07 03:04:41 UTC (rev 2293)
+++ trunk/refman-5.1/data-types.xml 2006-06-07 07:51:18 UTC (rev 2294)
@@ -4706,6 +4706,11 @@
<literal>TEXT</literal> column accounts for only five to nine
bytes toward this size.
</para>
+
+ <indexterm>
+ <primary>MySQL Cluster</primary>
+ <secondary>storage requirements</secondary>
+ </indexterm>
<para>
<emphasis role="bold">Important</emphasis>: For tables using the
@@ -4724,6 +4729,25 @@
(<literal>INT</literal>) column types each require 4 bytes storage
per record.
</para>
+
+ <para>
+ In addition, when calculating storage requirements for Cluster
+ tables, you must remember that every table using the
+ <literal>NDBCluster</literal> storage engine requires a primary
+ key; if no primary key is defined by the user, then a
+ <quote>hidden</quote> primary key will be created by
+ <literal>NDB</literal>. This hidden primary key consumes 31-35
+ bytes per table record.
+ </para>
+
+ <para>
+ When calculating Cluster memory requirements, you may find useful
+ the <filename>ndb_size.pl</filename> utility which is available on
+ <ulink url="http://forge.mysql.com/">MySQLForge</ulink>. This
+ Perl script connects to a current MySQL (non-Cluster) database and
+ creates a report on how much space that database would require if
+ it used the <literal>NDBCluster</literal> storage engine.
+ </para>
<indexterm>
<primary>numeric types</primary>
Property changes on: trunk/refman-5.1/images
___________________________________________________________________
Name: svn:ignore
+ *.bak
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2294 - in trunk: refman-4.1 refman-4.1/images refman-5.0 refman-5.0/images refman-5.1 refman-5.1/images | jon | 7 Jun |
