On Wed, Oct 07, 2009 at 12:01:53PM -0400, Steve Scaffidi wrote: > What's the interest out there for a several-order-of-magnitudes-faster > set of export-import scripts a-la RT::Extension::RT2toRT3 ? > > I currently have code capable of exporting the data from an RT > database with over 181,000 tickets and over 117,000 user accounts in > under four hours. > > The import script is not yet complete, but I'm shooting for similar > performance gains. All that's left is the ticket import which is > proving to be more difficult to get right (with the necessary > performance) than I initially hoped. If anybody has a *much* faster > means of importing the tickets themselves, I would love to integrate > that code! > > The intermediate data format is *exactly* the same as produced by the > scripts in RT::Extension::RT2toRT3. > > My versions of these scripts only work on postgresql, but they could > probably be modified to work just as well on mysql with little effort.
I would definitely be interested. I'm currently working on an RT2 to RT3 upgrade with around 500,000 tickets and without any tuning the import seems to be taking around a week (I think the export took around 8-12 hours). Our preferred database is PostgreSQL. This was with the latest devel release of RT::Extension::RT2toRT3. -- Dominic Hargreaves, Systems Development and Support Team Computing Services, University of Oxford _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
