Is there a way to deactivate an Eventhouse/KQL DB?

[arpost]

Greetings, all. I have eventhouses and KQL DBs in Dev and Test workspaces that are part of a deployment pipeline. They generate capacity usage even though no data is flowing in and no one uses them. I want to deactivate or turn off the Dev/Test objects until we want to use them for code changes for deployments so Prod isn't broken.

Is there a way to do this?

[Murtaza_Ghafoor]

In short: There is no single "Deactivate" button for a KQL Database or Eventhouse. Because these services provide real-time, "always-on" performance, they naturally generate idle compute costs.

However in this case you need pay as go capacity where you can pause the capacity when at night and over the weekends to save the cost up to 60 %.

Or you can delete the dev wc and recreate when require, unfortunately  there is no other option available, thanks

[v-nmadadi-msft]

Hi @arpost 

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

[v-nmadadi-msft]

Hi @arpost 

I wanted to check if you had the opportunity to review the valuable information provided by @svelde . Please feel free to contact us if you have any further questions.

Thank you.

[svelde · Accepted solution]

Hello @arpost ,

welcome to this Microsoft Fabric community forum. 

The Eventhouse acts like a computing cluster for timeseries data.

At cluster level, the UI offers the 'Always-on' ability:

When you enable this option, the Eventhouse cluster will run at 100% continuously:

This is because by default, your eventhouse will 'optimize cost by suspending the service when not in use'.

So, if you have highly time-sensitive systems that can't tolerate this latency, use Always-On. 

As part of that always-one scenario, you can provide a minimum consumption.

This setting gives the option to secure capacity when you have unpredictable queries or ingestion loads and need to ensure adequate performance:

That said, you are pointing to an dev/test environment. 

Unlike Azure Data Explorer, an Eventhouse cannot be paused. You have to rely on that cost optimization by suspending the service when it's not in use.

If you have multiple dev/test workspaces having their own Eventhouse, consider sharing the 'costs' by bringing all KQL databases together under one cluster.

As another alternative, because Fabric capacities can be paused, putting an Eventhouse (together with eg. Eventstream and Activator) in a separate capacity could work for you.

--

If this answer helps you, a thumbs-up or marking it as accepted answer is appreaciated.