Can I create external views in synapse from multiple data sources?

Gustavo Adolfo Alemán Sánchez 40 Reputation points
2024-07-10T00:58:48.06+00:00

Hi, I have data from different azure regions and my idea to decrease overhead is to use just synapse workspace with multiple external data sources and create the external tables for each of them, since I can't put all the data into a same location for compliance rules

After that step, create a serverless view with the union of each of the data sources to allow an easy data consumption in Power BI and avoid having multiple connections

Is this plan feasible or is there a better approach?

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,883 questions
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.
4,638 questions
0 comments No comments
{count} votes

Accepted answer
  1. phemanth 8,245 Reputation points Microsoft Vendor
    2024-07-10T04:27:16.65+00:00

    @Gustavo Adolfo Alemán Sánchez

    Thanks for using MS Q&A platform and posting your query.

    Your plan to use Azure Synapse Workspace with multiple external data sources and create serverless views for Power BI consumption is absolutely feasible and a good approach for your scenario with compliance restrictions. Here's a breakdown of the pros and cons:

    Pros:

    • Reduced overhead: By keeping data in its original location, you avoid unnecessary data movement and associated costs.
    • Compliance adherence: You can maintain compliance with regional data residency requirements.
    • Centralized management: Synapse Workspace provides a central platform to manage and query data from different sources.

    Simplified Power BI consumption: Serverless views offer a single connection point for Power BI, improving data accessibility.

    Cons:

    • Potential latency: Querying data across regions might introduce slight latency compared to co-located data.

    Increased complexity: Managing linked services and external tables for various sources adds some complexity.

    Alternative approaches (consider if latency is a major concern):

    Data federation: Azure Data Factory can virtually integrate data without physically moving it, offering a lower latency option. Hybrid approach: Combine Synapse with Azure Data Share to securely share data across regions while keeping it in its original location.

    Overall, your plan is a solid solution for your specific needs. If latency is a critical factor, explore the alternative approaches as well.

    Here are some additional resources that you might find helpful:

    Hope this helps. Do let us know if you any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

    0 comments No comments

0 additional answers

Sort by: Most helpful