Re: Remedy 6.3 Slow Searches
Also I should note that if you do add indexes for the query you need to ensure that table statistics are updated for the Query Optimizer to recognize and utilize the new index tables. Thanks Peter Lammey ESPN MIT Technical Services & Applications Management 860-766-4761 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of patrick zandi Sent: Wednesday, February 07, 2007 2:07 PM To: arslist@ARSLIST.ORG Subject: Re: Remedy 6.3 Slow Searches ** Indexes could be either out of date (forcing a full) or your query is inefficient.. I would never show all tickets (15K) unless very specifically asked.. I would show users ticket within 30 days, and another tab showing every ticket with a warning.. but that is just a bad idea in the first place.. Just an Idea.. On 2/7/07, Tanner, Doug <[EMAIL PROTECTED]> wrote: ** 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 gene ushinsky OIT - Service Desks Support Manager [EMAIL PROTECTED] | MB 161A | 801.422.2716 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. __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ -- Patrick Zandi __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" <>
Re: Remedy 6.3 Slow Searches
Also we do not auto refresh the tables (Refresh on Entry Change). We use Active Links to populate a table only when a User selects the tab it is on. Fred From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of patrick zandi Sent: Wednesday, February 07, 2007 1:07 PM To: arslist@ARSLIST.ORG Subject: Re: Remedy 6.3 Slow Searches ** Indexes could be either out of date (forcing a full) or your query is inefficient.. I would never show all tickets (15K) unless very specifically asked.. I would show users ticket within 30 days, and another tab showing every ticket with a warning.. but that is just a bad idea in the first place.. Just an Idea.. On 2/7/07, Tanner, Doug <[EMAIL PROTECTED]> wrote: ** 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 gene ushinsky OIT - Service Desks Support Manager [EMAIL PROTECTED] | MB 161A | 801.422.2716 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. __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ -- Patrick Zandi __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" <>
Re: Remedy 6.3 Slow Searches
Indexes could be either out of date (forcing a full) or your query is inefficient.. I would never show all tickets (15K) unless very specifically asked.. I would show users ticket within 30 days, and another tab showing every ticket with a warning.. but that is just a bad idea in the first place.. Just an Idea.. On 2/7/07, Tanner, Doug <[EMAIL PROTECTED]> wrote: ** 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 * gene**ushinsky *OIT - Service Desks Support Manager [EMAIL PROTECTED] | MB 161A | 801.422.2716 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. __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ -- Patrick Zandi ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" <>
Re: Remedy 6.3 Slow Searches
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" <>
