Can I schedule how often a connected source refreshes in iDBQuery?

Yes — you can set a refresh schedule per source, and iDBQuery also refreshes on demand. Live databases and warehouses are queried in place so they're always current; file, folder and API sources can re-ingest on an interval (for example nightly) or be refreshed manually whenever you need.

How a source stays current depends on its type, and iDBQuery handles both cases so your answers reflect the latest data.

  • Live databases and warehouses — MySQL, Postgres, SQL Server, Snowflake, BigQuery, and the like — are queried in place every time you ask, so there's nothing to refresh: you always get current numbers.
  • File, folder and API sources — CSV/Excel, a folder of documents, or a REST API — are ingested, so you can set a refresh schedule (for example, re-sync a REST API nightly or an uploaded folder on a chosen interval), or trigger a manual refresh whenever the underlying data changes.

You set this per source when you connect it, and can change it later. Scheduled refreshes mean recurring reports and live dashboards keep updating without anyone re-running an import by hand. The differentiator holds throughout: iDBQuery keeps one live queryable model across all sources, and every figure stays cited back to its exact source row, so a refreshed dashboard is still fully auditable. Combine a nightly-synced API with an always-live database in the same question and iDBQuery reasons across both — no ETL, no separate scheduler to maintain. In a VPC or air-gapped deployment, refreshes run entirely inside your environment.

Updated 2026-06-22