Issue with partitioned views/snapshot tables in azure synapse/ADLS

Phil Haywood 0 Reputation points

There seems to be an issue with the partitioned views (which run off the snapshot csv's in ADLS) for our data (we use Azure Synapse Link for Dataverse). Querying these views doesn't fail, but it cannot read all records in an entity, which is causing massive issues with our reporting. The non-partition tables appear to be fine, but as Microsoft recommends using the partitioned views for reporting, this would be a lot of work to re-write all our code!

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
3,805 questions
{count} votes

2 answers

Sort by: Most helpful
  1. PRADEEPCHEEKATLA-MSFT 70,016 Reputation points Microsoft Employee

    @Phil Haywood - I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer .

    Ask: Issue with partitioned views/snapshot tables in azure synapse/ADLS.

    Solution: Issue appears to have been fixed! Counts are now are match for partitioned vs. near real time (non-partitioned) tables.

    If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

    If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue.

    Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.

  2. Nandan Hegde 27,241 Reputation points MVP

    Hello All,

    We have an active ticket with MSFT on this issue and for now the issue seems to have been resolved.

    Note :It was resolved in morning but reoccured and now seems to be resolved again.

    Would keep this chat active on any updates