Gene,

            Most of this issue is caused by the Requesters Cases
(Table). You may wish to exclude that "User" Requester from the table
field refresh. Or change it to something like the below

 

 

 

 

Doug Tanner

Senior Developer

Remedy Skilled Professional (RSP)

Former RAC

(704) 328-3178

[EMAIL PROTECTED]

 

 

 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Gene Ushinsky
Sent: Wednesday, February 07, 2007 1:41 PM
To: arslist@ARSLIST.ORG
Subject: Remedy 6.3 Slow Searches

 

We use Remedy 6.3 and have close to 65,000 tickets in the database.
These are spread over thousands of users with most users having 10-15
tickets. However, we use a generic user account to login tickets that
don't belong to a particular user. This account has accumulated about
15,000 of the 65,000 tickets and it makes searching for tickets that
involve that account go rather slowly. Instead of immediate response
from the system while going down search results for a particular user,
it stalls for 5-30 seconds when the search results are generated on that
generic user. 

We are wondering what we can do to speed up these searches (if it is at
all possible) short of archiving the tickets for that user or creating a
new generic username. Any help would be appreciated.

Gene

geneushinsky
OIT - Service Desks Support Manager
[EMAIL PROTECTED] | MB 161A | 801.422.2716 

__20060125_______________________This posting was submitted with HTML in
it___

DISCLAIMER Important! This message is intended for the above named person(s) 
only and is CONFIDENTIAL AND PROPRIETARY. If you are not the intended recipient 
of this e-mail and have received it in error, please immediately notify the 
sender by return email and then delete it from your mailbox. This message may 
be protected by the attorney-client privilege and/or work product doctrine.  
Accessing, copying, disseminating or re-using any of the information contained 
in this e-mail by anyone other than the intended recipient is strictly 
prohibited. Finally, you should check this email and any attachments for the 
presence of viruses, as the sender accepts no liability for any damage caused 
by any virus transmitted by this email.  Thank you.


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

<<attachment: image001.jpg>>

Reply via email to