Post

Apparently someone from Microsoft told my client that Azure integration services is the best practice way of ingesting data into Fabric. My client is now confused why we're using things like mirroring and notebooks instead. ...I'm looking forward to the meeting with that Microsoft employee 🙃

1 repost20 likes

Mirroring isn't a great solution, at least until it provides an easy way to determine which data has changed. It could be a good solution, with some enhancements. Until then, it's suitable for people building DirectLake solutions directly on transactional data structures (bad) or toy sized systems.

Might also work somewhat if the source was already an analytic system but they rarely are. Adding a few system generated columns would make it much better for incremental loading, which you need for any sizable system where the data needs transformation.