It appears that Azure Synapse Link is fundamentally different than Export to Data Lake. If Microsoft is going to deprecate Export to Data Lake and replace it with Azure Synapse Link, I think they should function more similarly. We rely on the data lake for many processes like EDI, reporting, and alerts. Rebuilding everything we have in the lake using Azure Synapse Link is going to be a monumental effort since literally hundreds (if not thousands) of columns are missing. The Dirpartytable alone is missing around 140 columns. Everything we built in the lake is built on the axDB schema. Export to Data Lake mirrors that physical schema.
Howie Fu's approach is doable but will require a huge amount of development to replicate the hundreds of tables we currently rely on in the Lake. My frustration is likely due to my inexperience with the AOT since my experience is more DBA than x++. Is there any guidance available to help determine the derived tables that will be required? For example, in Dirpartytable, the column OMOPERATINGUNITTYPE is missing. I read that it exists on a derived table called omoperatingunit. However, that table doesn't exist in the axDB dbo schema. It does exist in the ax schema but it is empty. How do I determine where omoperatingunit resides? Thanks experts!