Thank you! I am in the exact same boat. I am looking for Fabric
"mirroring" support for the final impl. I will try to hold-on on
serverless for as long as I can until I am able to migrate. synapse-link
and mirroring are the right approach for me, my data gets updated
constantly.
Unfortunately I did not find a solution using this particular approach.
My end solution ended up being using Azure Data Factory and the CDC
feature. I setup a trigger and enabled change detection on the cosmos
container. When the changes happen I trigger a dataflow that copies the
data from cosmosdb...
Hi A93PTZZ I am looking at same scenario, did you figure out a smart way
to do this frequently w/o having to copy all data over and over all the
time? Thanks
Hi Bartosz We are trying to establish an OData Connection between
Microsoft Fabric and SAP ECC. Your blog has given us a lot of details.
In the picture that you provided above - Edit Linked Service. What
should we enter Service URL ? and how can we get that Service URL ?
This is great and will save significant time and effort. Question -(1)
will there a release for each feature branch?(2) release path should be
$(System.DefaultWorkingDirectory)/{Build_Alias}/{root folder}, right(3)
while specifying specific default branch, it seems it was deploying all
the artifacts...
Latest Comments