Perceptive Enterprise Search can index data from a variety of SQL data sources including desktop databases such as Microsoft Access, Paradox, dBASE, and FoxPro. Data from relational database servers (RDBMS) such as Microsoft SQL Server, Sybase and MySQL can be indexed via ODBC.
The process for setting up SQL indexing rules assumes that you have some knowledge of relational database concepts. You can nominate fields to be indexed, the order in which they should appear, the subset of records that should be included and how records are identified. Any number of data sources may be defined for each index.
You can join several tables together relationally and index them as a single entity within Perceptive Enterprise Search. For example, you might have a DOCTOR table that contains a list of doctor ID codes, names and addresses. You might also have a HOSPITAL table which contains hospital names and addresses, as well as the ID code of the chief surgeon. Using Perceptive Enterprise Search, you could index just the DOCTOR table or just the HOSPITAL table, or you could join the two together and index a composite view, showing hospital name (from the HOSPITAL table), chief surgeon name and phone number (from the DOCTOR table).
When you index SQL data, Perceptive Enterprise Search creates a file called ISYS.SQL, in which all the details are contained. This resides alongside the ISYS.CFG file for each index.
Perceptive Enterprise Search can index data from a variety of SQL data sources including desktop databases such as Microsoft Access, Paradox, dBASE, and FoxPro. Perceptive Enterprise Search can index most database systems that are accessible via ODBC, ADO or BDE.
To create, modify or delete a SQL Indexing rule, you need to switch to the SQL Rules list. You can achieve this by:
To create a new SQL rule:
To edit an existing SQL rule: