Forum Discussion
Mirror replication Premium extremely high consumption issue
Dear Community, We have switched on the CDF opportunity on 1-2 Mirrored database. We have noticed 30% minutes later we are almost knocked out the F32 license fully. We have on it extremnely sm...
Hello DSZ, could you share a bit more details regarding the setup you have. Source engine, and mirrored db setup.
It seems, you've applied some extras and charged for them.
By default and by the definition, mirroring is free of charge based on your caacity size where units equal to mirrored TB of data.
F32 => 32TB.
However, mirroring DB is fully managed by Microsoft and it's highly optimized for ingestions.
If you create notebook and run
%%sql
describe history `<workspace name>`.<mirrored db name>.<schema>.<table>
you will see lots of actions done for table performance optimization. If you set your history to more than 1 day (as it's by default), you might be charged exatly for keeping historical data as they are store in versions.
As an experiment, I would advise to stop mirroring the existing instance, create new one with default setup and keep it running for some time (few days). Maybe, it will be self healed 🙂
BR, Taras