a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }
Fabric Copy Job currently executes the entire copy job when the Run button is selected.
It would be very useful to have the ability to select one or more individual tables and execute only the selected tables without modifying the Copy Job configuration.
For example, if a Copy Job contains 10 tables and the mapping or configuration of only one table is modified, we may want to immediately run only that table to validate and apply the change. Currently, running the Copy Job also processes the other tables even though they have not been changed.
A simple implementation could be to add checkboxes next to each table in the monitoring/table list and provide an action such as "Run selected tables."
This would be particularly useful for:
- Re-running a table after changing its mapping or configuration
- Re-loading only the tables that require correction
- Testing changes without unnecessarily processing unrelated tables
- Reducing unnecessary data movement and processing
Ideally, the existing Run button would continue to execute the entire Copy Job, while a new Run selected tables option would execute only the tables selected by the user.
This would allow us to keep multiple related tables in a single production Copy Job while still having the flexibility to execute individual tables when needed.
