/
Source:Databases

Source:Databases

GEODI can also evaluate databases, i.e., structured data. Databases and their file information (including embedded) can be indexed (all tables and rows). With simple rules, you can limit tables, rows, or fields and set how rows are displayed to the user.

Use Project Wizard/Database connection to define the connection.

Conditions for connection

  1. Connection parameters (connection string) to the DB for read-only access

  2. Find the DB name on the table below if an additional driver is required (like ODAC for Oracle)

  3. Sampled data discovery decision (N record per table)

  4. The decision for Indexing and discovery of Embedded or linked files

Use “New Connection” to choose the database and define the connection string.

image-20231229-104301.png

Views can now be excluded if preferred. Since Views often contain data already present in other tables, excluding them will help reduce duplicate data discovery and improve performance.

image-20241126-115026.png

Supported DBMS

Some databases may require an extra driver to be installed. Please check the list below.

Supported DBMS

Client

Supported DBMS

Client

OLEDB

It may be possible to connect to database management systems or data sources that are not listed below using OLEDB. For this purpose, you can use a small utility included with the GEODI installation.

The utility located at:
<geodi>\x64\OleDbProviders.exe
lists the OLEDB providers registered on the system. The required provider must appear in this list. You may need to experiment with the detailed parameters in the GEODI connection settings.

For sources not listed, you may need to install an appropriate OLEDB driver. Please refer to the technical documentation provided by the data source.

ODBC

For ODBC sources, you can check whether the driver is registered using the ODBC Data Source Administrator.

For sources not listed, you may need to install the appropriate ODBC driver. Please refer to the technical documentation provided by the data source.

 

 

Elasticsearch

Connection String for GEODI

Dsn=my_elasticsearch_dsn;Driver={Elasticsearch Driver};description={my description};uid=username;pwd=password;server=your_es_host;port=9200

PostGres

No extra installation is required.

Microsoft SQL Server

No extra installation is required.

Sybase

ODBC driver installation is required.

Oracle (OleDB)

Additional Oracle .NET and Visual Studio ODAC Downloads ODAC OUI and ODAC 12.1.0.2.4 can be downloaded from the following link:
Additional Oracle .NET and Visual Studio ODAC Downloads

The downloaded ODAC 12.1.0.2.4 package should be extracted to a directory.

Run CMD as Administrator, navigate to the directory where ODAC 12.1.0.2.4 is located, and execute the following command: install.bat all C:\oracle\odac odac_home

  1. all: Installs all components.

  2. C:\oracle\odac: Target directory for the installation.

  3. odac_home: Oracle Home name (you can define this).

  4. true: Installs required dependencies.

DB2

Oledb Driver must be installed.

https://www.microsoft.com/en-us/download/details.aspx?id=100917#:~:text=Microsoft%20OLE%20DB%20Provider%20for%20DB2%20works%20with%20Microsoft%20SQL,tools%20to%20IBM%20Db2%20databases.

Oracle BigData

Microsoft Hive ODBC Driver must be installed.

https://www.microsoft.com/en-us/download/details.aspx?id=40886

SqLite

No extra installation is required.

Shape File

No extra installation is required.

CSV File

No extra installation is required.

KML File

No extra installation is required.

SQLCE, SQL express

No extra installation is required.

Kafka

No extra installation is required.

Excel

Access Database Engine 2010 must be installed.

https://www.microsoft.com/en-us/download/details.aspx?id=13255

MS Access

Access Database Engine 2010 must be installed.

https://www.microsoft.com/en-us/download/details.aspx?id=13255

Cassandra

OLEDB or ODBC driver is required

Download Cassandra Drivers & Connectors | CData Software

MongoDB

OLEDB or ODBC driver is required

ODBC Driver for MongoDB - Fast Access From ODBC-Compliant Tools and Languages

Alternative Connection Methods

Other than using the project wizard

  1. File-based ones such as SQLite, MDB, and AccDB are indexed automatically when found in a directory and don't have a password. You may define DBMeta for them.

  2. You must use Project Wizard for Excel files to be indexed as structured content.

  3. Settings made with Project Wizard/Database can be saved in *.xDeceConnection format. These files are automatically processed. It is a portable and secure way of defining connections.

Indexing DBs

  1. The default behavior is to crawl all tables and rows.

  2. Tables must have primaryKey by default. You may choose to index tables w/o a primary key also.

  3. You may choose a sampling mode, as only the selected number of rows is indexed in each table.

  4. You may choose a subset of tables.

  5. You may limit columns by their names.

  6. You may define SQLs to change content to be indexed

  7. Embedded files are indexed with proper definitions

  8. File paths are processed with proper definitions

  9. If rows have some permission information you may utilize it with proper definitions. (There are also different ways to define applications like CRM and ERP as sources.)

  10. When you search in GEODI, Each row is content. You may define the name and appearance of a record database or table-wise.

Trouble Shooting

  1. The connection string may not be correct. You should test it before saving the project, which you can do now.

  2. Check the permissions

  3. Index error logs should be checked. You can examine the errors received in the scan with the developer report via GEODI.

  4. DBmetas may not be correct.

  5. Jsettings files should be syntax validated, you can use JSON Formatter & Validator site for this validation.

  6. Check the correctness of the column, table, and GEODI project names and their names on the Table/Column/Project database.

GEODI crawls file-based databases like SQLite or Access by name in default settings. You may install a module from DECE-STORE to override this setting and discover rows.

  1. You should define DB meta to do that. This page explains ho to create DB metas.

  1. By default, GEODI crawls all tables and rows. You may use sampled discovery or narrow the target.

  2. Your DB might also be serving another application.

  3. GEODI indexing speed options might be at low, increase it.

  4. The GEODI Server might be running on a low-capacity machine with insufficient memory or a slow disk. Please check the system requirements page.

After the initial index, each subsequent indexing (scheduled or manual) can create versions for tables without a primary key. This does not affect discovery results or reports but only impacts the GEODI index size.

GEODI indexing logs errors for such tables. Check the error log to see which tables are affected.

By default, GEODI requires a primary key (PK) column to be present. This situation does not occur unless otherwise specified. Additionally, you can choose to add a PK to your tables (best practice). For GEODI, a PK column has a unique value in each row.

If your table has a PK but you are still encountering errors, then the primary key column name must be recorded in GEODI by defining a DB meta.

By default, GEODI reads all rows with the same permissions. To set a row-based permission, please use DB meta.

 

FAQ

Yes. Using DBmeta, you can read rows or embedded file permissions from a database.

Yes. With a few simple DBmeta definitions, you may index those files. In this case, GEODI will show the row and file separately. You will be able to query the file using DB attributes.

It is possible. You index the CRM database with a simple DB meta and set a link that opens the original CRM apps. The CRM app should have a simple URL(query string) that can be built using the attributes.

DB Meta Definitions