Performance - Using SetSearchExpr method over SetSearchSpec, especially with regard to case-insensitive queries
Last updated on JULY 20, 2016
Applies to:Siebel Tools - Version 7.5.1 SIA  and later
Information in this document applies to any platform.
Release(s):V6 (Siebel 2000-Enterprise), V7 (Enterprise), V8 (Enterprise)
Database(s):DB2, Informix, Microsoft, Oracle, Sybase
App Server OS(s):AIX, Solaris, Windows 95, WFW 3.11, Windows NT, Windows 2000, Windows 3.1, HP-UX
Latest release tested against:V8 (Enterprise)
Keywords:SVB, eScript, performance, setsearchexpr, setsearchspec
Checked for Relevance on 11-06-2011
This document was previously published as Siebel FAQ 1455.
Checked for relevance on 13-Sep-2013.
When querying a business component in code, the criteria for retrieval can be set using either the SetSearchSpec method or the SetSearchExpr method. SetSearchSpec sets the search specification for a particular field, whereas SetSearchExpr allows for the setting of an entire search expression on the business component.
The Siebel application architecture has been designed to generate efficient SQL. Under certain circumstances, a LIKE operator is created in the SQL statement. For example, if the parameter CaseInsensitive has been set to TRUE in the configuration (.cfg) file, an instruction like:
In some situations, a script might have to search for the exact string (case sensitive). How can this be achieved without changing the global CaseInsensitive parameter?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms