Share
Report
1We are trying to use ASL with an Serverless Azure Synapse Pool following the steps in this document.
According to this document, //learn.microsoft.com/en-us/power-apps/maker/data-platform/export-data-lake-faq#what-date-and-time-formats-can-be-expected-in-exported-dataverse-tables , CreatedOn should be datetimeoffset datatype.
After running this for a week, the synapse external tables and the _partitioned views often differ and change "CreatedOn" between datetimeoffset and datetime2. There are even differences in data types between the External Table and the _partitioned views! For example, currently CreatedOn in dbo.account is datetimeoffset while dbo.account_partitioned is datetime2. Also, dbo.incident in both external table and _partitioned view is datetime2 but give it an hour and one (or both) will change.
We need the data types of these columns to remain static so we can point to one of the objects in another database, as an external table. As soon as we align all the objects to the current data types, they change in an hour or so. Is this by design? Is our only option to try the other route of using ADF to load this data from the Data Lake into Azure SQL staging tables, according to this article? learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-pipelines?tabs=data-factory
All responses (
Answers (
