Skip to main content
To homepage To homepage
Solved

Timextender & Fabric Mirrored database

D
Starter

Hello!

I am using Timextender to get MS Dynamics data to an Azure SQL DB.

I would now like to use the Fabric Mirrored Database function (https://learn.microsoft.com/en-us/fabric/database/mirrored-database/overview) to integrate the tables from the Azure SQL DB in a Fabric Warehouse. However I get this error upon execution in Timextender:

Cannot truncate table 'dbo.D_Date' because it is published for replication or enabled for Change Data Capture.

 

Is there a way around this or will the Fabric DB mirroring function not work with the Timextender/Azure-DWH tables?

Thanks for any advice! 

Best answer by rory.smith

Hi,

I assume you are aware of all the current limitations of Fabric Mirroring? No private link, only the first 500 tables, etc?

 

If TX is pushing data from source into Azure SQL DB it will want to truncate tables to furnish reloads from source. Tables cannot be truncated if they are replicated (you would need to do a much slower DELETE). As Fabric Mirroring only works against the write primary you cannot use something like a named replica in Hyperscale to work around this. The only thing you could do is enable Mirroring, capture all data, disable mirroring, reload TX.

View original
    Did this topic help you find an answer to your question?

    2 replies

    rory.smith
    TimeXtender Xpert
    Forum|alt.badge.img+7
    • rory.smith
    • TimeXtender Xpert
    • 658 replies
    • Answer
    • June 19, 2024

    Hi,

    I assume you are aware of all the current limitations of Fabric Mirroring? No private link, only the first 500 tables, etc?

     

    If TX is pushing data from source into Azure SQL DB it will want to truncate tables to furnish reloads from source. Tables cannot be truncated if they are replicated (you would need to do a much slower DELETE). As Fabric Mirroring only works against the write primary you cannot use something like a named replica in Hyperscale to work around this. The only thing you could do is enable Mirroring, capture all data, disable mirroring, reload TX.

    D
    Starter
    • dash7
    • Author
    • Starter
    • 1 reply
    • June 19, 2024

    Hi Rory, thanks for you reply!

    Ok, sounds like the best solution would be to be able to schedule the DB mirroring in Fabric  - which you can not do at the moment if I am not mistaken. Too bad….

    Reply


    Most helpful members this week

    Terms and ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings