Mirror replication Premium extremely high consumption issue

Hi DSZ,

Hi

Thank you for sharing the additional information, and thanks to Lozovskyi  for the helpful explanation about mirroring internals and history retention. The insight about retained table history and background optimization activity affecting capacity usage is useful, especially since mirrored databases handle multiple internal processes for performance and recovery. Testing with a new mirrored instance using default settings, as suggested, should help determine if the issue is related to configuration or history retention, or if it's due to an unexpected backend behavior. Since the capacity consumption is unusually high, it’s still advisable to continue the investigation with a support ticket so the product team can confirm whether the CU usage matches expected behavior for your setup.

Thank you.