Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
sawilliams
Frequent Visitor

Does Fabric duplicate data when creating a table from a Parquet file?

Hi Community,

I'm working on a POC for a simple data ingestion pipeline in Microsoft Fabric. My process is as follows:

  1. Read a CSV from a shortcut to ADLS2
  2. Convert it to Delta Parquet
  3. Save it in the FILES path of the Lakehouse
  4. Create a table from the stored Parquet in the Fabric portal

However, after creating the table, I noticed that the Parquet files also appear in the TABLES path, even though I initially saved them in FILES. Is Fabric duplicating the Parquet files when creating the table?

 

Would it be better to save the Parquet files directly in the TABLES path instead of FILES to avoid redundancy?

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @sawilliams 
Thank you for reaching out microsoft fabric community forum.

Yes, Microsoft Fabric does duplicate the data when creating a table from a Parquet file. This happens because the data is initially stored in the FILES path and then copied to the TABLES path when creating the table.

To avoid redundancy, it would indeed be better to save the Parquet files directly in the TABLES path from the start. This way, you won't have duplicate copies of your data

If you need any further assistance or have any questions, please feel free to reach  us.

If this solution helps, please consider giving us Kudos and accepting it as the solution so that it may assist other members in the community.

Thank you.

 

View solution in original post

1 REPLY 1
Anonymous
Not applicable

Hi @sawilliams 
Thank you for reaching out microsoft fabric community forum.

Yes, Microsoft Fabric does duplicate the data when creating a table from a Parquet file. This happens because the data is initially stored in the FILES path and then copied to the TABLES path when creating the table.

To avoid redundancy, it would indeed be better to save the Parquet files directly in the TABLES path from the start. This way, you won't have duplicate copies of your data

If you need any further assistance or have any questions, please feel free to reach  us.

If this solution helps, please consider giving us Kudos and accepting it as the solution so that it may assist other members in the community.

Thank you.

 

Helpful resources

Announcements
FabCon Global Hackathon Carousel

FabCon Global Hackathon

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!

September Fabric Update Carousel

Fabric Monthly Update - September 2025

Check out the September 2025 Fabric update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.