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
rs] Ticket history table full error) 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 pr

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
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 after about a year of usage and I'd like to prune that down or at