[exo-jcr-commits] exo-jcr SVN: r5259 - jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration.
do-not-reply at jboss.org
do-not-reply at jboss.org
Mon Dec 5 04:48:13 EST 2011
Author: dkuleshov
Date: 2011-12-05 04:48:13 -0500 (Mon, 05 Dec 2011)
New Revision: 5259
Modified:
jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration/jdbc-data-container-config.xml
Log:
EXOJCR-1668: docbook modified
Modified: jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration/jdbc-data-container-config.xml
===================================================================
--- jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration/jdbc-data-container-config.xml 2011-12-02 15:43:25 UTC (rev 5258)
+++ jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration/jdbc-data-container-config.xml 2011-12-05 09:48:13 UTC (rev 5259)
@@ -83,36 +83,11 @@
</listitem>
</itemizedlist></para>
- <para><note>
- <para>Please note, that JCR requires at least READ_COMMITED isolation
- level and other RDBMS configurations can cause some side-effects and
- issues. So, please, make sure proper isolation level is configured on
- database server side.</para>
- </note><note>
- <para>One more mandatory JCR requirement for underlying databases is a
- case sensitive collation. Microsoft SQL Server both 2005 and 2008
- customers must configure their server with collation corresponding to
- personal needs and requirements, but obligatorily case sensitive. For
- more information please refer to Microsoft SQL Server documentation
- page "Selecting a SQL Server Collation" <ulink
- url="http://msdn.microsoft.com/en-us/library/ms144250.aspx">here.</ulink></para>
- </note><note>
- <para>Be aware that MyISAM is not supported due to its lack of
- transaction support and integrity check, so use it only if you don't
- expect any support and if performances in read accesses are more
- important than the consistency in your use-case. This dialect is only
- dedicated to the community.</para>
- </note><note>
- <para>RDBMS reindexing feature use queries based on LIMIT and OFFSET
- clauses which are not enabled by default for DB2. However, you can
- ensure they are enabled by executing the following <programlisting>$ db2set DB2_COMPATIBILITY_VECTOR=MYS
-$ db2stop
-$ db2start</programlisting></para>
- </note> Each database software supports ANSI SQL standards but also has
- its own specifics. So, each database has its own configuration in eXo JCR
- as a database dialect parameter. If you need a more detailed configuration
- of the database, it's possible to do that by editing the metadata
- SQL-script files.</para>
+ <para>Each database software supports ANSI SQL standards but also has its
+ own specifics. So, each database has its own configuration in eXo JCR as a
+ database dialect parameter. If you need a more detailed configuration of
+ the database, it's possible to do that by editing the metadata SQL-script
+ files.</para>
<para>SQL-scripts you can obtain from jar-file
exo.jcr.component.core-XXX.XXX.jar:conf/storage/. They also can be found
@@ -250,14 +225,6 @@
</tr>
</table>
- <note>
- <para>* MyISAM is not supported due to its lack of transaction support
- and integrity check, so use it only if you don't expect any support and
- if performances in read accesses are more important than the consistency
- in your use-case. This dialect is only dedicated to the
- community.</para>
- </note>
-
<para>In case the non-ANSI node name is used, it's necessary to use a
database with MultiLanguage support[TODO link to MultiLanguage]. Some JDBC
drivers need additional parameters for establishing a Unicode friendly
@@ -284,6 +251,81 @@
</section>
<section>
+ <title>General recommendations for database configuration</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>Please note, that JCR requires at least READ_COMMITED isolation
+ level and other RDBMS configurations can cause some side-effects and
+ issues. So, please, make sure proper isolation level is configured on
+ database server side.</para>
+ </listitem>
+ </itemizedlist>
+
+ <section>
+ <title>DB2 configuration</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>RDBMS reindexing feature use queries based on LIMIT and OFFSET
+ clauses which are not enabled by default. However, you can ensure
+ they are enabled by executing the following <programlisting>$ db2set DB2_COMPATIBILITY_VECTOR=MYS
+$ db2stop
+$ db2start</programlisting></para>
+ </listitem>
+ <listitem>
+ <para>Be aware, when using RDBMS for reindexing need to run
+ "RUNSTATS ON TABLE <scheme>.<table> WITH DISTRIBUTION
+ AND INDEXES ALL" for JCR_SITEM (or JCR_MITEM) and JCR_SVALUE (or
+ JCR_MVALUE) tables.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section>
+ <title>MySQL configuration</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>MyISAM is not supported due to its lack of transaction support
+ and integrity check, so use it only if you don't expect any support
+ and if performances in read accesses are more important than the
+ consistency in your use-case. This dialect is only dedicated to the
+ community.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section>
+ <title>PostgresSQL configuration</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>Be aware, when using RDBMS for reindexing need to set
+ "enable_seqscan" to "off" or "default_statistics_target" at least
+ "50"</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section>
+ <title>MS SQL configuration</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>One more mandatory JCR requirement for underlying databases is
+ a case sensitive collation. Microsoft SQL Server both 2005 and 2008
+ customers must configure their server with collation corresponding
+ to personal needs and requirements, but obligatorily case sensitive.
+ For more information please refer to Microsoft SQL Server
+ documentation page "Selecting a SQL Server Collation" <ulink
+ url="http://msdn.microsoft.com/en-us/library/ms144250.aspx">here.</ulink></para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </section>
+
+ <section>
<title>Multi-database Configuration</title>
<para>You need to configure each workspace in a repository. You may have
More information about the exo-jcr-commits
mailing list