How many pipeline copy activities can be writing into the same Lakehouse Table at once?

[v-cyu]

As titled

[Houston-ho]

A bit curious why you need multiple pipeline copy activities into same table in lake house.
I guess all those pipelines are having different data sources or transformation, but with same schema in the destination lakehouse table, plsu you are talking about "append" not "overwrite", otherwise, that looks a bit strange.

If all the above assumptions are true, that make sense.

And yes, seems no stated limitation, but i believe your might consider what file format are actually stored in the Onelake, if they are column based like Parquet, ok, if they are partitioned appropriately, even better. However, if your lake house table is just a huge CSV file, i doubt the performance issue on multiple pipelines writing on it.

[Anonymous · Accepted solution]

Hi, @v-cyu 

From the information I found, it appears that there isn't a specific limit on the number of pipeline copy activities that can write into the same Lakehouse Table at once.

More information can be found in the following documentation: Configure Lakehouse in a copy activity - Microsoft Fabric | Microsoft Learn

Best Regards,

Community Support Team _Charlotte

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.