How does iDBQuery keep connected sources up to date?
iDBQuery keeps live databases current automatically because it queries them in place — every question hits the source, so answers always reflect the latest data. For files and REST APIs, you set a recurring sync schedule that refreshes the ingested data so it stays up to date without manual work.
How sources stay current depends on their type, but in every case iDBQuery handles it without you maintaining a pipeline.
- Live databases — MySQL, Postgres, MongoDB and SQL warehouses are queried in place. Because iDBQuery runs each question against the source, answers always reflect the current state of the database; there is nothing to refresh.
- REST APIs — set a recurring sync schedule and iDBQuery re-fetches the endpoint automatically so the connected API data stays fresh.
- Files and folders — re-ingest when the underlying files change, or schedule recurring syncs so updated exports are picked up.
For connectors that need refreshing, iDBQuery runs syncs on a schedule in the background, so the data behind your questions, dashboards and reports keeps pace with reality. You configure the cadence once. This is a deliberate contrast to a warehouse approach, where keeping data current means building and babysitting ETL jobs. Here, live sources are inherently current, and the few sources that need refreshing are handled on a timer you control — so the answers and dashboards your team relies on don't quietly go stale.
Updated 2026-06-22