Running a Copy Job against a PostgreSQL database quickly fails with the error message "too many connections", indicating that PostgreSQL is rejecting the connection attempts. This could easily be solved by limiting the maximum amount of connections that Fabric establishes against PostGreSql. It would be a great feature to have such a configuration possibility on a Copy Job.
No CommentsBe the first to comment
Recent ideas
Add "Collapse all / Expand all" to the Queries pane in Power Query Editor
Hi Fabric Community, I suggest adding a "..." menu beside Queries(n])with Collapse all and Expand all. Current state: With many queries, every group and Helper Queries folder is expanded. My 8...DataVitalizer1 day agoSuper UserNew12Views0likes0CommentsAdd Automated Pre-Upgrade Compatibility Assessment for Fabric Spark Runtimes
Microsoft Fabric should provide an automated compatibility assessment before a workspace, Environment, notebook, or Spark Job Definition is upgraded to a newer Fabric Runtime. Spark runtime upgra...mourakshit1 day agoNew MemberNew6Views0likes0CommentsSupport Creator-Independent Managed Identity and Ownership Transfer for Fabric Operations Agents
Microsoft Fabric Operations Agents should support an enterprise identity and ownership model that is independent of the individual user who originally created the agent. Today, an Operations Agent r...mourakshit1 day agoNew MemberNew11Views0likes0Comments