Can't create a Lakehouse destination

[TePe]

Hi,

I tried to take the WWI Data Sample (used a Copy Activity in a Pipeline to bring the dimensions and facts into the Lakehouse) and do some transformations on top of the fact table. However, first I tried to just read the fact table and write it to another one. This already fails for me because when I want to create a destination (on the bottom right of the screen) to the Lakehouse, the little green circle besides "Create a new connection" circles forever... 

What can I do?

Thanks,

Thomas

[Element115]

I just experienced the spinner circling forever as well just now after creating a Data destination. My setup is different than yours. Nonetheless, I did a page refresh, and the issue went away.  What went away also was the query in the dataflow and I had to recreate it from scratch.  So always a good idea to backup all your query M code somewhere local, just in case.

[pqian_MSFT]

Would you mind collecting some diagnostics so we can look into this further

1. in the Options -> Diagnostics window, copy the session ID and share it here

2. If possible, repro the problem and export the browser network logs. Share it with me via DM or email (pqian at microsoft). The network log contains active tokens so take care of not sending it publicly.

[TePe · Accepted solution]

I get closer to the solution, if I find some time I'll try to replicate... It looks that the problem appears when you don't have any meaningful transformation in the Dataflow. Meaning: just add a source and try to add a destination and then the problem appeared for me. As soon as I added a transformation I could add the destination successfully. But as I said, I need to replicate that again... And in my case the Dataflow ran for more than 1 hour for the WWI fact table (about 50mio records, just reading the records without transformation but with staging enabled, no destination) which I think is REALLY slow...

[pqian_MSFT]

BTW, if you do not need staging, please turn it off, it'll help in speeding up the overall ingestion speed since we do not need to copy the data twice.

[pqian_MSFT]

Interesting observation, that is definitely not expected - if you manage to reproduce the issue again, make sure you share the session IDs and/or network traces