Re: [Mailmanager-users] MM 2.0.9 PSQL 8.0.6 Woes...

[SJ.Stanaitis <sst...@dp...>]

Kevin,

Thanks for getting back to me so quick.  I ended up running a "VACUUM FULL;"
on the database, after which full performance was restored.  I will check
out that SQL file to see how to properly eliminate tickets moving forward.

Have a good weekend!

Sam

SJ.Stanaitis - Network Administrator
Decorative Product Source E-commerce Network

-----Original Message-----
From: Kevin Campbell [mailto:ke...@lo...] 
Sent: Friday, February 02, 2007 10:38 AM
To: SJ.Stanaitis
Cc: 'Logicalware Mailmanager-users'
Subject: Re: [Mailmanager-users] MM 2.0.9 PSQL 8.0.6 Woes...

On Fri, Feb 02, 2007 at 08:20:54AM -0500, SJ.Stanaitis wrote:
> (Accidentally posted with wrong subject earlier)
> 
> I had set up a script on my Slackware box to re-assign tickets older than
1
> year to a specific Archive user, as I discovered that either due to
> performance issues on my system or MM when an active user gets a LARGE
> number of tickets (say over 20K) the entire system would slow down.
> 
> Long story short, the script ran the other night, or tried to, and now MM
is
> CRAWLING.  The queries still go through without error, but the PSQL
database
> is taking its sweet time to respond.  I'm running PSQL 8.0.6 and MM 2.0.9.
> 
> Awhile back I had inquired as to how I might delete tickets from the
> database manually, and did not receive a response so I used the following
> query:
> 
> DELETE FROM mm_ticket WHERE date_closed LIKE "200x- %";
> 
> Now I've discovered that while the mm_ticket table gets updated, and the
> tickets are no longer displayed, the messages are still stored in the
> mm_message table.  Could that be part of the speed issue, all those
> un-linked messages?
> 
> Is there any way to sync up the two tables, or export the active tickets,
> wipe the tables, and restore them?

Sam,

Please see the deleteTickets.sql method which should show what tables
need to be altered in order to delete tickets. Deleting tickets from the
database will improve performance, particularly in the 2.0 series where
the full text index is stored on the mm_ticket table.

As for performance issues, there are many performance issues which exist
in the 2.0 series, which were resolved in 2.1 an 2.2 which is in
development. I would certainly recommend looking at 2.1 if you are
having problems. 20k ticket is not a relatively large number of tickets
compared to our production installations so this should be something
which can be resolved.

Regards,
Kevin

--
Kevin Campbell
Chief Technical Officer - Logicalware Ltd
Office: +44 (0)131 225 5422
US & Canada: (347) 293 0699
Kev...@lo...
----------------------------------------------
Logical Progression LTD trading as Logicalware Ltd, Registered in the UK
at 23 Manor Place, Edinburgh, EH3 7DX, Company Number SC234177

www.logicalware.com