RE: Database pruning (was: RE: [otrs] Ticket history table full error)

2007-02-09 Thread Jason B. Loven
day, February 08, 2007 8:57 AM To: User questions and discussions about OTRS.org Subject: Re: Database pruning (was: RE: [otrs] Ticket history table full error) Jason B. Loven wrote: > Is there a quick way to tell? You could for instance run an SQL query like this: SELECT COUNT(*

Re: Database pruning (was: RE: [otrs] Ticket history table full error)

2007-02-08 Thread Nils Breunese (Lemonbit)
Jason B. Loven wrote: Is there a quick way to tell? You could for instance run an SQL query like this: SELECT COUNT(*) FROM otrs.ticket; Nils Breunese. PGP.sig Description: Dit deel van het bericht is digitaal ondertekend ___ OTRS mailing lis

RE: Database pruning (was: RE: [otrs] Ticket history table full error)

2007-02-08 Thread Jason B. Loven
uning (was: RE: [otrs] Ticket history table full error) OK... I bit the bullet and did the max_rows change and all seems well. Next question: Is there a way to prune the database or to archive history out of the database to get things down in size? My history file is currently at 4GB aft

RE: Database pruning (was: RE: [otrs] Ticket history table full error)

2007-02-07 Thread Maurice James Ny
How many tickets do you have? _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason B. Loven Sent: Wednesday, February 07, 2007 11:19 AM To: User questions and discussions about OTRS.org Subject: Database pruning (was: RE: [otrs] Ticket history table full error

Database pruning (was: RE: [otrs] Ticket history table full error)

2007-02-07 Thread Jason B. Loven
User questions and discussions about OTRS.org Subject: [otrs] Ticket history table full error Anyone know how to fix this? We're running 2.0.4 and I saw this showing up in the cron logs. I've disabled cron for now but obviously that's bad because now we're having to manually

[otrs] Ticket history table full error

2007-02-07 Thread Jason B. Loven
Anyone know how to fix this? We're running 2.0.4 and I saw this showing up in the cron logs. I've disabled cron for now but obviously that's bad because now we're having to manually handle the incoming mail queue for our support. Here's the error... DBD::mysql::db do failed: The table 'tick