In default settings, 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. By default, GEODI crawls all table tables and all 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 is one that 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.

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

Yes. with 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 and 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 build built using the attributes.