Forum Discussion
Copy Job - Limiting Connections to Source System
We are currently attempting to ingest data from a PostgreSQL database into Fabric using a Copy Job. The setup process is quite straightforward; however, when executing the job, it often fails with the error message "too many connections", indicating that PostgreSQL is rejecting the connection attempts.
Is there a way to limit the maximum number of parallel connections that the Copy Job initiates?
6 Replies
- tayloramy
Super User
Hi sberge,
I don't think you can do this for a copy job, but you can do it for a copy activity in a pipeline. This is called out in the Microsoft docs here: Copy activity performance and scalability guide - Microsoft Fabric | Microsoft Learn
I think switching over to a pipeline with a copy activity rather than a copy job would be best for your requirements here, until Microsoft adds this level of control to Copy Jobs.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Thank you for your reply. Switching to copy activities within a pipeline requires significantly more manual effort to set up the entire copy process. It’s quite unfortunate that Microsoft doesn’t support such a basic feature in a copy job.
- tayloramy
Hi sberge,
I recommend you post an idea here: Fabric Ideas - Microsoft Fabric Community
Hopefully it will gain traction and Microsoft will look at implementing this.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
v-dineshyaCommunity Support
