We use the special 'Search Criteria' field (ID 1005). I put that
display-only field on forms I want to lock down searches on. Then I
setup an active link, firing On Search, that throws an error if 'Search
Criteria' = $NULL$ and a select set of other fields are also null. I
handpick the other fields to include those that are indexed and other
commonly used fields that might be selective. That way they have to
either specify a value in one of those other fields, or use the advanced
search bar. I realize the advanced search bar still completely opens the
door to bad searches, but it turns away most bad searches. I also have a
Max Get List on the server as a safety net.

I used to watch for some common bad searches with SQL Profiler and I
think we were getting hundreds per day. This reduced it to probably less
than 50. It was a difference maker with over 600 concurrent users and
over 3,000,000 rows in that table.

Chad Hall  
(501) 342-2650

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96
CS/SCCE
Sent: Tuesday, July 22, 2008 3:18 PM
To: [email protected]
Subject: Re: Unqualified Searches in Very Large Enterprises -- Thoughts,
Please

Oh...clicked SEND too soon...your idea is good but people who use the
Advanced Search Bar would fall victim to the error.

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W
Sent: Tuesday, July 22, 2008 3:11 PM
To: [email protected]
Subject: Re: Unqualified Searches in Very Large Enterprises -- Thoughts,
Please

** 
Is there any specific fields they add data to before searching?  We have
a similar situation where tech will add data to at least 1 of probably
10 different fields.  We have an AL that fires on search and display's
an error if all 10 of them are NULL.
 
The problem with the limit rows returned setting is it does not alter
the call to the database. It only grabs the top x rows from the database
results so even with a setting of 1000 the database pulls all 150,000
rows where Remedy only display's 1000.
 
Fred

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96
CS/SCCE
Sent: Tuesday, July 22, 2008 2:25 PM
To: [email protected]
Subject: Unqualified Searches in Very Large Enterprises -- Thoughts,
Please



Hi everyone:

 

I wanted to get everyone's take on this thorny issue...I know this
matter has been discussed many times before, but I wanted to put a new
twist on it.

 

Specifically, I wanted to get anyone and everyone's thoughts on the
problem of unqualified searches in a large enterprise.  Specifically,
suppose the following: Suppose you have a custom app being used in a
very large environment.  Suppose in that environment you have
established a ticket isolation system by setting hidden fields on the
form on SEARCH.  Tickets are isolated by every company within the
enterprise.

 

Now, each company has in excess of 150,000 tickets, and there are 20
companies.  The problem is, techs are accidentally clicking the SEARCH
button without any qualification...kicking off what is *seemingly* an
unqualified search.  But the search is not truly unqualified because
fields are getting set on SEARCH to effect the ticket isolation.  But
the problem remains - such a search goes out and attempts to fetch
150,000+ tickets.  Several techs accidentally doing this at once (we
have 800+ techs, so the possibility of techs doing this is pretty high)
causes the server to slow way down.

 

Thoughts on how to minimize this issue? Hopefully I've described the
problem well enough.

 

TIA,

Norm 

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___ 

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
*************************************************************************
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be
legally privileged.

If the reader of this message is not the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.

Thank you.
*************************************************************************

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

Reply via email to