Is there any harm in allowing unqualified searches in a production environment.
We had been told that we should disallow this for production, but we are
finding that in order to leverage some of the reporting capabilities
(dynamically choosing parameters such as groups) this option is
If you have and use AIE and the CMDB, you will have to allow them. It
breaks things if it is turned off.
Rick
On Aug 8, 2012 2:54 PM, "Hodgdon, Paul" wrote:
> **
>
> Is there any harm in allowing unqualified searches in a production
> environment. We had been told that w
ction Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Hodgdon, Paul
Sent: Wednesday, August 08, 2012 2:54 PM
To: arslist@ARSLIST.ORG
Subject: unqualified searches
**
Is there any harm in allowing unqualified searches in a production environment.
We had been told th
Shellman, David
Sent: Wednesday, August 08, 2012 12:57 PM
To: arslist@ARSLIST.ORG
Subject: Re: unqualified searches
**
You may see performance hits if some one creates a malformed search that
returns every record that was created in the table.
For tables with not much data no problem. If you&#x
9, 2012 at 12:23 AM, Hodgdon, Paul wrote:
> **
>
> Is there any harm in allowing unqualified searches in a production
> environment. We had been told that we should disallow this for production,
> but we are finding that in order to leverage some of the reporting
> capabil
Scutchings
Sent: Wednesday, August 08, 2012 3:15 PM
To: arslist@ARSLIST.ORG
Subject: Re: unqualified searches
**
What we did to get around this issue is only allowed it on one of our servers,
server group of 4 with 3 out of 4 on the load balancer. That way the people
that need the ability to do
Dave - that is my understanding too. I allow unqualified searches, actually
this was inherited, and don't see a problem. In general I think people search
for something (in Remedy). I would suggest not setting up searches behind
buttons/active links that you would expect large results. P
Hello Paul,
There are ways around the "unqualified search" issues as you hit upon.
Personally, in our org we found unqualified searches caused degradation in
our performance and at times locking up the mid-tier.
To solve our problem our admin has put in a get list limit. But we
h the list limit, so
this is limited on the database and those extraneous rows are never sent to the
AR server.
We have two AR servers, one is used for user connections, the other is for
AIE\CMDB\Bulk Updates. For the user facing server we allow unqualified
searches, but limit the rows to
Has anyone been able to figure out a relatively quick way to identify Set
Fields/ Push Fields qualifications in the database/workflow export that have
No qualification?
I'm not sure if there is a pattern in the internal qualifier that would
indicate that there is or is not a qual.
I'm also
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
e, 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
>
Behalf Of Axton
Sent: Tuesday, July 22, 2008 2:33 PM
To: arslist@ARSLIST.ORG
Subject: Re: Unqualified Searches in Very Large Enterprises -- Thoughts,
Please
Some things that come to mind:
- Force the use of a preference server, force the value of max
returned entries to 1000 or the likes
- Set a
; From: Action Request System discussion list(ARSList)
> [mailto:[EMAIL PROTECTED] On Behalf Of Axton
> Sent: Tuesday, July 22, 2008 2:33 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: Unqualified Searches in Very Large Enterprises -- Thoughts,
> Please
>
> Some things that come to mind
st(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook
Sent: Tuesday, July 22, 2008 2:56 PM
To: arslist@ARSLIST.ORG
Subject: Re: Unqualified Searches in Very Large Enterprises -- Thoughts,
Please
**
That's the beauty of using the preference values - they can be set
differently - and enf
ssion 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: arslist@ARSLIST.ORG
Subject: Unqualified Searches in Very Large Enterprises -- Thoughts,
Please
Hi everyone:
I wanted to get everyone's take on this thorny issu
uly 22, 2008 2:33 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: Unqualified Searches in Very Large Enterprises -- Thoughts,
> Please
>
> Some things that come to mind:
> - Force the use of a preference server, force the value of max
> returned entries to 1000 or the likes
> - Set a ha
able.
-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: arslist@ARSLIST.ORG
Subject: Re: Unqualified Searches in Very Large Enterprises -- Thoughts,
Please
**
Is there any
To: arslist@ARSLIST.ORG
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
: 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: arslist@ARSLIST.ORG
Subject: Re: Unqualified Searches in Very Large Enterprises -- Thoughts,
Please
Oh...clicked SEND too soon...your idea
;
07/22/2008 01:18 PM
Please respond to
arslist@ARSLIST.ORG
To
arslist@ARSLIST.ORG
cc
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.
Yes, AND...not OR...correct...typo on my part.
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W
Sent: Tuesday, July 22, 2008 3:33 PM
To: arslist@ARSLIST.ORG
Subject: Re: Unqualified Searches in Very Large
On Behalf Of Grooms, Frederick W
Sent: Tuesday, July 22, 2008 3:11 PM
To: arslist@ARSLIST.ORG
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
being
table scanned.
You could also just set the setting for blocking unqualified searches. It
is simple enough to by-pass that setting, but it has to be a conscious
effort. All they have to do is enter != $NULL$ in the ID field.
Just a few ideas.
HTH,
Brian
On Tue, Jul 22, 2008 at 2:06 PM, Kaiser
24 matches
Mail list logo
