[Bps-public-commit] r10983 - rt2-to-rt3/trunk

[falcone at bestpractical.com]

Author: falcone
Date: Mon Mar  3 10:17:26 2008
New Revision: 10983

Modified:
   rt2-to-rt3/trunk/   (props changed)
   rt2-to-rt3/trunk/README

Log:
 r29998 at ketch:  falcone | 2008-03-03 10:16:45 -0500
 * advise people to add an Index and make the import faster


Modified: rt2-to-rt3/trunk/README
==============================================================================
--- rt2-to-rt3/trunk/README	(original)
+++ rt2-to-rt3/trunk/README	Mon Mar  3 10:17:26 2008
@@ -39,6 +39,13 @@
 
 Install rt3. Let it set up your rt3 database.
 
+You probably want to take this opportunity to add an Index to your
+CachedGroupMembers table.  If you're running PostgreSQL, you should already
+have a relevant index.  For MySQL or Oracle, this should help avoid
+table scans during the import.
+
+ALTER TABLE CachedGroupMembers add index MemIm (MemberId, ImmediateParentId);
+
 Tell dumpfile-to-rt-3.0 where your RT libraries live. (Edit the 'use lib' lines)
 
 If your RT instance contains tickets encoded in a characterset other than