Forum Discussion

pmscorca's avatar
pmscorca
Icon for Post Prodigy rankPost Prodigy
1 year ago
Solved

Having a warehouse as a destination

Hi,

using eventstream I've noticed that it isn't possible to choice a warehouse as a destination.

Which is the reason about it?

I think that it could be very useful to write also on a warehouse.

Thanks

  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi pmscorca ,

     

    The primary reason for this limitation is likely due to the architecture and design focus of Microsoft Fabric. Eventstream is designed to handle real-time data ingestion, transformation, and routing, which aligns well with destinations like Lakehouse and Eventhouse that are optimized for real-time analytics and storage. These destinations allow for efficient querying and analysis using tools like Kusto Query Language (KQL) and Delta Lake format, which are well-suited for handling streaming data. However, Warehouse only supports T-SQL, not KQL.

    Please refer:

    Lakehouse vs Data Warehouse vs Real-Time Analytics/KQL Database: Deep Dive into Use Cases, Differences, and Architecture Designs | Microsoft Fabric Blog | Microsoft Fabric

     

    However, your suggestion to include traditional data warehouses as a destination is valid and could indeed be beneficial for many use cases. 

    You can submit an idea for it at Home (microsoft.com) and wait for users with the same needs as you to vote for you to help make it happen as soon as possible.

     

    Best Regards,

    Neeko Tang

    If this post  helps, then please consider Accept it as the solution  to help the other members find it more quickly. 

1 Reply

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi pmscorca ,

     

    The primary reason for this limitation is likely due to the architecture and design focus of Microsoft Fabric. Eventstream is designed to handle real-time data ingestion, transformation, and routing, which aligns well with destinations like Lakehouse and Eventhouse that are optimized for real-time analytics and storage. These destinations allow for efficient querying and analysis using tools like Kusto Query Language (KQL) and Delta Lake format, which are well-suited for handling streaming data. However, Warehouse only supports T-SQL, not KQL.

    Please refer:

    Lakehouse vs Data Warehouse vs Real-Time Analytics/KQL Database: Deep Dive into Use Cases, Differences, and Architecture Designs | Microsoft Fabric Blog | Microsoft Fabric

     

    However, your suggestion to include traditional data warehouses as a destination is valid and could indeed be beneficial for many use cases. 

    You can submit an idea for it at Home (microsoft.com) and wait for users with the same needs as you to vote for you to help make it happen as soon as possible.

     

    Best Regards,

    Neeko Tang

    If this post  helps, then please consider Accept it as the solution  to help the other members find it more quickly.