Setting Up Search

There are two main ways to search for text in an iBase database, Search 360 (in SQL Server databases only) or Word Search. An index must exist before users can use either search method.

Search indexes allow users to search multiple fields in multiple entity and link types, and can include information that is stored in attached documents. Database designers can define the rules used to build and search an index.

Using Search 360

Search 360 can be used to search any type of text field in SQL Server databases, including documents and charts, using a range of techniques that allow for:

Any number of words in a phrase
Typing mistakes (for example typing ROBETRSON instead of ROBERTSON, or Danielsmith instead of Daniel Smith)
Variations in spellings and variations based on how words are pronounced (for example typing PETERSON instead of PEDERSON because, the two names sound the same)
Synonym matching (for example, Mike and Michael are synonym matches)
Variations in word order (for example "Joyce Gallagher" and "Gallagher, Joyce" are exact matches)
Allowances are made for punctuation and accents (for example Francoise and Françoise are exact matches)
Records directly related to the main search (that is, just one link away from a record found by the main search)

Using Word Search

Word Search can be used to search a database of any format using:

Exact words
Wildcards
Synonym matching
Soundex

When matched text is found, it is highlighted in context in the document. Word Search also allows users to browse the index and find text based on the number of times they occur or by their leading characters.

What is not searched?

The search methods do not search:

The targets (records, files or URLs) of Hyperlink fields, only hyperlink text is searched.
In Search 360, document types for which there is no installed iFilter on the machine that performs the indexing.
Number type fields, including numbers, dates, time zones, system and calculated fields.