https://community.databricks.com/t5/get-started-discussions/when-are-dlt-going-to-support-multiple-targets/m-p/73458#M3110 <P>Due to the limitations with all output data needing to be stored in one target we have stopped using DLT until more flexibility is added.&nbsp;</P><P>If anyone has a workaround we are open to suggestions.&nbsp;</P> Wed, 12 Jun 2024 21:53:38 GMT Zavi 2024-06-12T21:53:38Z https://community.databricks.com/t5/get-started-discussions/when-are-dlt-going-to-support-multiple-targets/m-p/73458#M3110 <P>Due to the limitations with all output data needing to be stored in one target we have stopped using DLT until more flexibility is added.&nbsp;</P><P>If anyone has a workaround we are open to suggestions.&nbsp;</P> Wed, 12 Jun 2024 21:53:38 GMT https://community.databricks.com/t5/get-started-discussions/when-are-dlt-going-to-support-multiple-targets/m-p/73458#M3110 Zavi 2024-06-12T21:53:38Z https://community.databricks.com/t5/get-started-discussions/when-are-dlt-going-to-support-multiple-targets/m-p/75873#M3175 <P>Hi Zavi,<BR /><BR />One potential workaround is to establish multiple DLT pipelines, with each pipeline specifically configured to point to a unique target. This approach effectively allows for a diverse range of output data to be stored across various targets.</P><P>To manage these multiple pipelines efficiently, you can utilize Databricks Workflows. Workflows can orchestrate the execution of these pipelines, ensuring they operate in harmony and maintain the integrity of your data processes.</P><P><SPAN>Best regards, Rafael Ribeiro</SPAN></P> Wed, 26 Jun 2024 16:22:31 GMT https://community.databricks.com/t5/get-started-discussions/when-are-dlt-going-to-support-multiple-targets/m-p/75873#M3175 Rafael-Ribeiro 2024-06-26T16:22:31Z