Azure Database for PostgreSQL output from Azure Stream Analytics

You can use Azure Database for PostgreSQL as an output for data that is relational in nature or for applications that depend on the content being hosted in a relational database. Azure Stream Analytics jobs write to an existing table in PostgreSQL Database. The table schema must exactly match the fields and their types in your job's output.

Azure Database for PostgreSQL powered by the PostgreSQL community edition is available in two deployment options:

  • Single Server
  • Flexible Server

For more information about Azure Database for PostgreSQL please visit the: What is Azure Database for PostgreSQL documentation.

To learn more about how to create an Azure Database for PostgreSQL server by using the Azure portal please visit:


Managed identities for Azure Database for PostgreSQL output in Azure Stream Analytics is currently not supported.

Output configuration

The following table lists the property names and their description for creating an Azure Database for PostgreSQL output.

Property name Description
Output alias A friendly name used in queries to direct the query output to this database.
Subscription select the desired Azure Subscription.
Server or server group name A unique name that identifies your Azure Database for PostgreSQL server. The domain name is appended to the name of the server you provide. The server can contain only lowercase letters, numbers, and the hyphen (-) character. It must contain at least 3 through 63 characters.
Database The name of the database where you are sending your output
Username The username that has write access to the database. Stream Analytics supports only username/password authentication. The username should be in the "username@hostname" format for Single Server, "username" for Flexible server.
Password The password to connect to the database.
Table The table name where the output is written. The table name is case-sensitive. The schema of this table should exactly match the number of fields and their types that your job output generates.


Partitioning needs to enabled and is based on the PARTITION BY clause in the query. When the Inherit Partitioning option is enabled, it follows the input partitioning for fully parallelizable queries.

Next steps