PostgreSQL V2 Connector Not Appearing as Sink in Azure Data Factory

Question

PostgreSQL V2 Connector Not Appearing as Sink in Azure Data Factory

Mohan, Maddala Dharmendra 0

Hi Team,

We are working on a data integration pipeline using Azure Data Factory (ADF) to load data from Azure Data Lake (Zen2 Lake) into an on-premises PostgreSQL database using the PostgreSQL V2 connector.

Here’s our setup:

PostgreSQL version: 15+

ADF Connector: PostgreSQL V2

Integration Runtime: Self-hosted (version 5.54.9267.1)

Sink Dataset: Created using PostgreSqlV2Table type

Linked Service: Uses PostgreSQL V2 with SHIR

Source Dataset: DelimitedText from Azure Data Lake Storage Gen2

We are able to:

Preview data from the source

Validate the sink dataset independently

**Issue:**In the Copy Activity, the sink dataset (sink_ds_for_postgres) does not appear in the dropdown, and when attempting to add it manually via JSON, ADF Studio throws a "name is not allowed" error.

We’ve verified:

PostgreSQL version compatibility

SHIR connectivity and version

Dataset and linked service configurations

No regional limitations are documented

Could you please help us identify the root cause or confirm if this is a known issue?

Thanks,
Mohan

Manoj Kumar Boyini 330 Reputation points Microsoft External Staff Moderator

2025-10-22T10:39:21.01+00:00

Hi Mohan, Maddala Dharmendra,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
Thanks for sharing the details. I took a closer look at your setup, and this issue usually happens when ADF doesn’t properly recognize the PostgreSQL V2 connector as a valid sink.

Here are a few things you can double-check:

1.Dataset type – Open the dataset JSON and make sure it says "type": "PostgreSqlV2Table". Even a small mismatch (like PostgreSqlTable) can cause it not to appear as a sink.

2.Dataset name – Avoid using special characters or spaces in the dataset name. ADF will throw a “name not allowed” error if the name isn’t alphanumeric or includes symbols.

3.Integration Runtime – Make sure both your source and sink use the same Self-hosted Integration Runtime. If the source uses AutoResolveIR while the sink uses SHIR, ADF won’t list the sink dataset properly.

4.SHIR version – Double-check your SHIR version. PostgreSQL V2 sink support needs version 5.54.9267.1 or higher. Anything older might cause this behavior.

5.Try recreating the dataset – Sometimes recreating the sink dataset through the UI (instead of editing JSON) helps ADF register it correctly.

Once you verify these points, the PostgreSQL V2 sink should appear in the Copy Activity. Let me know how it goes we can look deeper if it still fails to show up.

Kindly let us know if the above helps or you need further assistance on this issue.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Thanks,
Manoj
Manoj Kumar Boyini 330 Reputation points Microsoft External Staff Moderator

2025-10-23T08:48:44.9333333+00:00

Hi Mohan, Maddala Dharmendra,

I hope the steps provided above were helpful. Please let me know if there's anything else I can assist you with.

Thanks,
Manoj
Mohan, Maddala Dharmendra 0 Reputation points

2025-10-23T09:32:00.4433333+00:00

i have used v2 connector and integration run time is also same as what u have mentioned i haven't included special characters,just now i can see this documentation from microsoft copy activity ,it don't supports sink operation to postgressql(https://free.blessedness.top/en-us/azure/data-factory/copy-activity-overview#supported-data-stores-and-formats), but from microsoft postgres document for data movement we can copy data to sink (https://free.blessedness.top/en-us/azure/data-factory/connector-postgresql?tabs=data-factory)

could you please validate both and let me know how can i resolve this issue ,and how to load data to postgres
Manoj Kumar Boyini 330 Reputation points Microsoft External Staff Moderator

2025-10-24T08:47:56.67+00:00

Hi Mohan, Maddala Dharmendra,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

Thanks,
Manoj

1 answer

Your answer

Manoj Kumar Boyini 330 Reputation points Microsoft External Staff Moderator

2025-10-22T10:39:21.01+00:00

Hi Mohan, Maddala Dharmendra,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
Thanks for sharing the details. I took a closer look at your setup, and this issue usually happens when ADF doesn’t properly recognize the PostgreSQL V2 connector as a valid sink.

Here are a few things you can double-check:

1.Dataset type – Open the dataset JSON and make sure it says "type": "PostgreSqlV2Table". Even a small mismatch (like PostgreSqlTable) can cause it not to appear as a sink.

2.Dataset name – Avoid using special characters or spaces in the dataset name. ADF will throw a “name not allowed” error if the name isn’t alphanumeric or includes symbols.

3.Integration Runtime – Make sure both your source and sink use the same Self-hosted Integration Runtime. If the source uses AutoResolveIR while the sink uses SHIR, ADF won’t list the sink dataset properly.

4.SHIR version – Double-check your SHIR version. PostgreSQL V2 sink support needs version 5.54.9267.1 or higher. Anything older might cause this behavior.

5.Try recreating the dataset – Sometimes recreating the sink dataset through the UI (instead of editing JSON) helps ADF register it correctly.

Once you verify these points, the PostgreSQL V2 sink should appear in the Copy Activity. Let me know how it goes we can look deeper if it still fails to show up.

Kindly let us know if the above helps or you need further assistance on this issue.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Thanks,
Manoj
Manoj Kumar Boyini 330 Reputation points Microsoft External Staff Moderator

2025-10-23T08:48:44.9333333+00:00

Hi Mohan, Maddala Dharmendra,

I hope the steps provided above were helpful. Please let me know if there's anything else I can assist you with.

Thanks,
Manoj
Mohan, Maddala Dharmendra 0 Reputation points

2025-10-23T09:32:00.4433333+00:00

i have used v2 connector and integration run time is also same as what u have mentioned i haven't included special characters,just now i can see this documentation from microsoft copy activity ,it don't supports sink operation to postgressql(https://free.blessedness.top/en-us/azure/data-factory/copy-activity-overview#supported-data-stores-and-formats), but from microsoft postgres document for data movement we can copy data to sink (https://free.blessedness.top/en-us/azure/data-factory/connector-postgresql?tabs=data-factory)

could you please validate both and let me know how can i resolve this issue ,and how to load data to postgres
Manoj Kumar Boyini 330 Reputation points Microsoft External Staff Moderator

2025-10-24T08:47:56.67+00:00

Hi Mohan, Maddala Dharmendra,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

Thanks,
Manoj

Answer 1

Hi Mohan, Maddala Dharmendra,

Thanks for sharing those details you are absolutely right to notice that difference in the documentation. I checked this closely, and here what’s really going on.

The PostgreSQL V2 connector currently supports reading data (source) only. It doesn’t support writing data to PostgreSQL (sink) in the Copy Activity, which is why your PostgreSqlV2Table dataset doesn’t appear in the sink dropdown, and why you get the “name not allowed” error when you try to add it manually. This isn’t a configuration issue on your side it’s just a limitation of the current V2 connector.

You have two possible ways to load data into PostgreSQL:

If your PostgreSQL database is hosted on Azure Use the Azure Database for PostgreSQL connector instead of the V2 one. It fully supports copy operations into PostgreSQL as a sink. Just create an AzurePostgreSql linked service and dataset, and select that in your Copy activity sink.

If your PostgreSQL database is on-premises You can connect through ODBC using your Self-Hosted Integration Runtime (SHIR).

Install the PostgreSQL ODBC driver on your SHIR machine.

  Create an ODBC linked service and an OdbcTable dataset for your target table.
  
     Use OdbcSink in your Copy activity. This is the supported way to write data to on-premises PostgreSQL from ADF.

The reason the docs seem confusing is because one page lists PostgreSQL in the general “supported data stores,” but the detailed PostgreSQL V2 connector page mentions that it works as a source only, not as a sink.

There’s nothing wrong with your setup. The connector itself just doesn’t support writes yet. Switching to the AzurePostgreSQL connector (for Azure) or ODBC (for on-prem) will solve this.

Do let us know if you have questions and queries.

Thanks,
Manoj

Share via

PostgreSQL V2 Connector Not Appearing as Sink in Azure Data Factory

1 answer

Your answer