March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
Register NowGet certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now
Hi to everyone
I'm a first timer with Data Factory though i'm pretty experienced with PowerBI power Query.
So i've created a dataflow gen2 that takes data from On-prem SQL server, prepares those into tables and loads to the destination of Lakehouse. Once executed I find on lakehouse not only those tables that I've ordered to create as a result of DataFlow execution but others with crazy letter-numerical names but with contents of those other tables i've ordered to create... what goes wrong?
THanks for support
Solved! Go to Solution.
looks like the problem was resolved by using another Lakehouse as a destination point. The new lakehouse is created by myself, while previous was created by my colleague. In new LH the problem is not present. DataFlow Gen2 remains all the same except having another LH as a destination point. HOpe it helps you to find a bug. If I can help you somehow, I'm available.
Sergey
found out that all of those are having parquet word in name... probably those are technical tables that should be created? Then the question is which one should I use to create a data model (star scheme) for PowerBI report?
Hi @SVVIS ,
Thanks for using Fabric Community.
Can you please share few screenshots with source tables and destination tables?
I need few more details regarding your ask inorder to guide you better.
Hi
Here are some screenshots of what you ask me (I hope I understood you well, but let me know if more or else is needed)
Much appreciated,
Sergey
Hi @SVVIS ,
Can you please share screenshots like this?
Tables at my lakehouse -
When I tried to reproduce your scenario, I am able to get 3 different tables without any issue.
I just want to know what is the step that created those parquet tables.
looks like the problem was resolved by using another Lakehouse as a destination point. The new lakehouse is created by myself, while previous was created by my colleague. In new LH the problem is not present. DataFlow Gen2 remains all the same except having another LH as a destination point. HOpe it helps you to find a bug. If I can help you somehow, I'm available.
Sergey
Hi @SVVIS ,
Glad to know that your query got resolved by changing it with new Lakehouse.
I am happy to guide you with your query. Please continue using Fabric Community for your further queries.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
Check out the October 2024 Fabric update to learn about new features.
User | Count |
---|---|
3 | |
2 | |
2 | |
1 | |
1 |
User | Count |
---|---|
6 | |
4 | |
3 | |
3 | |
3 |