Reporting database for dashboards
Records from 311, permitting and work orders are upserted nightly into SQL Server for Power BI reports.
Microsoft SQL Server and Azure SQL run many city systems: finance and HR reporting, older permitting and work order apps, and the reporting databases IT builds for dashboards. Most sit inside the city network.
SentraBridge reads tables or a read-only query, writes with insert, update or upsert, and handles geometry and geography columns. Connections are encrypted by default. Flows can start on Change Tracking, and the relay reaches servers behind the firewall.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Tables | read a table or a read-only query | insert, update, upsert | yes (changed-time column) | Any table you grant |
Records from 311, permitting and work orders are upserted nightly into SQL Server for Power BI reports.
Rows changed in a department's own SQL Server app start a flow that updates the 311 request.
CSV files dropped in SharePoint are loaded into a SQL Server table and archived.
Rows with coordinates are written with a geography column so the GIS team can map them.
Systems cities commonly connect with SQL Server, each with its own connector page.
Yes, through the relay. It runs inside your network, calls out over HTTPS, and reaches only the hosts you list. No inbound ports open.
Yes. Use SQL Server Change Tracking, or a changed-time column polled on a schedule.
No. Use a SQL login. Windows logins aren't supported from containers.
Yes. The same connection works with SQL Server and Azure SQL.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.