jpelham1
2 years agoNew Member
Status:
Under Review
Update Copy Data Activity to allow for adding columns to multiple tables
Currently custom columns can be added to one table, but when importing multiple tables and needing to add the same columns to every table, this is not possible. Our specific use case is that we are loading multiple tables from our SQL server into a Lakehouse and want to add a Load_Date column and a Pipeline_RunID column to every table that is loaded. When loading one table this is very easy, but when we load more than one table, the current functionality of the mapping tab within the copy data activity does not allow this.
1 Comment
- fbcideas_migusrNew MemberStatus added:Under Review
Recent ideas
Set SQL analytics endpoint access mode (User's identity) via REST API and Terraform
The SQL analytics endpoint enforces OneLake security only in User's identity access mode. The only documented way to choose the mode is the Security tab in the portal (Data access mode settings). Not...smorimoto1 hour agoNew MemberNew1View0likes0CommentsFabric Copy Jobs desperately need basic editability after creation.
Requiring users to recreate an entire Copy Job just to change something as fundamental as the source connection or connection URL is unnecessarily restrictive and creates significant maintenance over...mpersha23 hours agoRegular VisitorNew6Views0likes0Comments