Can I connect Microsoft SQL Server or Azure SQL to iDBQuery?
Yes — iDBQuery connects to Microsoft SQL Server and Azure SQL as standard SQL databases through its database connector. You enter the server, database and read-only credentials, iDBQuery introspects the schema, and it becomes part of one live queryable model you ask in plain language. No ETL needed.
Both on-prem Microsoft SQL Server and cloud Azure SQL connect through iDBQuery's standard database connector — they're SQL databases, so the same connect-and-introspect flow applies without any special build.
- You'd connect SQL Server by supplying the server/host, port, database and a read-only login (SQL or Azure AD auth); Azure SQL uses your fully-qualified server name.
- iDBQuery introspects the tables, views and columns, applies its semantic layer to interpret naming, and adds the database to your one live queryable model.
- Ask a question like *"Which accounts are overdue by more than 60 days?"* and iDBQuery writes the T-SQL, runs it, and returns a cited number, chart, table or dashboard.
Unlike bolting a BI tool on top, iDBQuery queries in place and cites every figure back to the exact rows, so finance and ops can audit any answer. Because the database is now part of one model, a single question can span SQL Server and a spreadsheet, an Azure SQL instance and a REST API together — no staging database or pipeline. If the server sits behind a firewall or inside Azure, deploy iDBQuery in the same VPC or air-gapped so the connection never leaves your network.
Updated 2026-06-22