Integration · Azure SQL and PostgreSQL

    Your own database, only read.

    Datahub connects to Azure SQL Database and PostgreSQL for insights, metrics and flows. Every statement is checked before it leaves: only reads get through.

    SELECT region, SUM(amount)ReadDELETE FROM ordersNot a readRefusedDatabase
    • Read-only

      Never writing

      Datahub refuses any statement that is not a read, before it reaches the database.

    • Closed twice

      The database guards too

      Give the connection read rights only, and the database enforces that nothing changes as well.

    • AI

      Metadata only at first

      AI assistants see schemas, tables and column types by default, no rows.

    What you build with it

    Insights, metrics and flows on your own tables.

    • “Revenue per month, as an insight on finance's dashboard.”

      Insight
    • “Open orders, as a metric with a fixed definition.”

      Metric
    • “A flow that fetches the new customers every morning.”

      Flow
    • “Which columns are in the invoices table?”

      Schema
    • “How many orders came in yesterday?”

      With data on
    • “Stock value per branch, next to figures from other sources.”

      Insight
    What AI sees

    Two switches. The stricter one applies.

    An AI assistant only sees the database's structure by default. Rows come along only when the connection is set to metadata and data and the organisation allows it too. If either is set to metadata only, it stays that way.

    ConnectionMetadata and dataOrganisationMetadata onlyThe stricter applies: AI sees metadata only

    The organisation says no, so it stays at metadata.

    • Azure SQL

      Azure SQL Database

      Sign in with a service principal from Entra ID or with a SQL user.

      • The db_datareader role is enough
      • Open the firewall for Datahub's address
      • Up to 10,000 rows, stopped after 50 seconds
    • PostgreSQL

      PostgreSQL

      Sign in with a database role and password, encrypted over TLS.

      • Grant the role SELECT only
      • Choose the SSL mode, Require at least
      • The same features as Azure SQL
    • Not yet

      Alerts

      Alerts on Azure SQL and PostgreSQL come later. Alerts on a query result already work on Microsoft Fabric.

    Where you use it

    One connection, three places.

    • Insights

      Dashboards on your database

      Insights and dashboards read live from your own tables.

    • Metrics

      One definition per figure

      A metric records how a figure is calculated, so everyone sees the same number.

    • Flows

      Data in your process

      A flow reads a query's result and carries on with it.

    How to connect your database

    From database to first insight in four steps.

    1. 01

      Create a reader

      Create a user or role with read rights only, or a service principal for Azure SQL.

    2. 02

      Grant access

      Open the firewall for Datahub's address, or choose the SSL mode for PostgreSQL.

    3. 03

      Enter the details

      Enter the server, the database and the sign-in details in Datahub.

    4. 04

      Save and test

      Save the connection and test it. A successful test shows which login it uses.

    Frequently asked questions

    What administrators ask before they connect.

    Next step

    Put your database to work, without risk.

    An intro call maps which databases you run and what it takes to connect them.