Can iDBQuery change or write to my database?
No — iDBQuery is read-only by design. It queries your data to answer questions but does not write, update or delete anything in your source systems, and it connects using read-only access wherever possible, so pointing it at production carries no risk of unwanted changes.
A common and reasonable worry is 'if I connect this AI to my database, could it change something?'. With iDBQuery the answer is no — it is built to read, not write.
- Read-only by design. iDBQuery generates SELECT-style queries to answer questions. It does not issue writes, updates or deletes to your sources.
- Least-privilege connections. Wherever possible it connects using read-only credentials, so the account it uses cannot modify data even if something tried to.
- Safe on production. Because it only reads, you can point it at a live production database, or a read replica, without risk of it altering records.
- Transparent. You can see the exact SQL it ran, so there is never a hidden operation against your data.
This is fundamental to how iDBQuery is meant to be used: it is an analytics layer over your systems of record, not a tool that operates on them. For example, an analyst can safely explore the production orders database, ask dozens of questions, and know that nothing they ask can accidentally change an order. If your governance requires it, use a dedicated read-only user and iDBQuery works exactly the same. The guarantee here is architectural — the product does not need write access to do its job, so it does not take it.
Updated 2026-06-22