Re: [rt-users] sqlite
On Wed, Sep 23, 2009 at 10:50:40AM -0400, Jesse Vincent wrote: On Wed, Sep 23, 2009 at 10:29:03AM -0400, Mauricio Tavares wrote: Tom Lahti wrote: Sorry. What I meant to say is RT's SQLite support - I _love_ SQLite for all sorts of applications. multi-user apps with SQLite are totally doable -- you just need to be careful with write concurrency ;) If you leave synchronous writes on, you're limited on transaction speed. A commit takes at least two full drive rotations, so for a 7200rpm drive you can only do 60 transactions per second. Not terribly scalable :) I am in a small shop (12 people tops). If we end up having 60 tickets per minute, I would be happily amazed and glad to upgrade to mysql or something else. No, really, don't do that. We haven't tested RT 3.x on SQLite in a production environment. That's not a supported configuration. I have no idea how badly it might hurt you. with 300 tickets on a machine running on xen, it's been unusable. took about 15 seconds just to show a ticket. the problem was disk io. underlying disk space was a hardware raid1 on SAS disks. now with mysql, it takes about 2 seconds to show a ticket. mk ___ 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
Re: [rt-users] sqlite
On Tue, Sep 22, 2009 at 11:40:03AM -0700, Tom Lahti wrote: SQLite is primarily intended for development and testing environments. It's not well-suited to a multi-user production environement for RT. Actually, I think SQLite's mission is to provide a lightweight database for individual use applications. It's used by a lot of such things such as Apple Mail, Safari, Firefox, Google Gears, and the Skype client. But it certainly isn't robust enough for the enterprise side of things. Google Gears on SQLite sure, but Google itself? Skype client yes, but Skype servers? Not gonna happen. RT is very slow when using sqlite. I've installed rt3.6 from debian with sqlite and after about 300 tickets, I was forced to go through a painful process of migrating data to mysql. With mysql rt is about 10 times faster. mk ___ 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
[rt-users] wrong utf8 encoding in subject header field
Hi. I've noticed that after my migration from sqlite to mysql, there started appearing wrong Subject header fields in emails sent by rt. I'm using rt3.6 from debian lenny. I've looked into the database and given Attachments have this wrong Subject in the Subject column. The problem I'm unable to resolve is, if this can be a problem when someone sends email as a reply to this ticket, their email client creates this wrong Subject field and rt just copies that, or if it is a problem with utf8 encoding inside perl. does anyone have similar problems? thanks mk ___ 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
[rt-users] custom fields in transactions, sum of those in ticket header
Is it possible(without having to program it) to have a custom field for ticket transaction and have a sum of those fields in the ticket header, the same way as time worked works? thanks mk ___ 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
[rt-users] how to migrate data from sqlite to mysql
Hi. I've installed rt3.6 on debian lenny, where sqlite is a default db backend. Since then we've started using ticketing quite a lot and sqlite stopped being fast enough. I've been trying to migrate data from sqlite to mysql by dumping sql from sqlite, changing it so that mysql can read it and importing it into mysql database created by dbconfig on debian(which calls rt-setup-database). I usually can read all the ticket data, but users are damaged and I can't create tickets/modify tickets/give tickets to other users. rt-dump-database doesn't dump all of the database data so it can't be used. Is there some way to migrate that data from sqlite db to mysql? Is there such a big difference in the table setup, that those two databases are incompatible? thanks martin ___ 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
Re: [rt-users] how to migrate data from sqlite to mysql
On Wed, Aug 19, 2009 at 02:38:21PM +0100, Dominic Hargreaves wrote: On Wed, Aug 19, 2009 at 02:38:05PM +0200, Martin Kraus wrote: Hi. I've installed rt3.6 on debian lenny, where sqlite is a default db backend. Since then we've started using ticketing quite a lot and sqlite stopped being fast enough. I've been trying to migrate data from sqlite to mysql by dumping sql from sqlite, changing it so that mysql can read it and importing it into mysql database created by dbconfig on debian(which calls rt-setup-database). I usually can read all the ticket data, but users are damaged and I can't create tickets/modify tickets/give tickets to other users. rt-dump-database doesn't dump all of the database data so it can't be used. Is there some way to migrate that data from sqlite db to mysql? Is there such a big difference in the table setup, that those two databases are incompatible? Hi, I'm afraid I don't recall all of the details but we did document what should be a migration at http://pkg-request-tracker.alioth.debian.org/3.6-databases/ What exactly do you see as missing from the dump? Note the discussion on the predefined system objects on that page and possible workaround. I've read that doc but running rt-dump-database produces -rw-r--r-- 1 root root17361 2009-08-19 16:14 r -rw-r--r-- 1 root root 277401 2009-08-19 16:14 r0 -rw-r--r-- 1 root root 38651270 2009-08-19 02:11 rtdb-2009-08-19.sql where the file r is rt-dump-database r r0 is rt-dump-database 0 r0 rtdb-2009-08-19.sql is an sql dump of the entire database, that has 40MB in sqlite the rt dumps contain things like users and custom fields but do not contain actual tickets. Maybe I've misunderstood how it works. mk ___ 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
