Wanted to get feedback from the community and support engineers as to what conditions could cause this anomaly to happen:
Mongosqld.exe finds all 21 of our collections/tables that have data and creates the relational schemas correctly.
There is however one table that sometimes it thinks does not have data.
This is a collection/table and not an object.
Apiedb.applications does in fact have data.
There are no changes being made to configurations to the connector or ODBC. No other deltas.
Mongosqld.exe sometimes thinks that a table DOES NOT have data:
2022-02-17T08:00:23.311-0800 D SCHEMA [sampler] mapping schema for namespace “apiedb”.“applications”
2022-02-17T08:00:23.407-0800 D SCHEMA [sampler] skipping namespace “apiedb”.“applications”: no documents found
Sometimes thinks that the table DOES have data:
2022-02-24T09:37:27.540-0800 D SCHEMA [mapping] mapped new table “applications”
2022-02-24T09:37:27.540-0800 D SCHEMA [sampler] finished mapping schema for namespace “apiedb”.“applications”
Any thoughts feedback greatly appreciated!