> For the complete documentation index, see [llms.txt](https://docs.seemoredata.io/external-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seemoredata.io/external-docs/fundamentals/our-features/waste-reduction/remove-auto-clustering.md).

# Remove Auto-Clustering

Find tables where Snowflake auto-clustering costs more than it is worth and drop the clustering key to stop paying for it.

## Overview

Remove Auto-Clustering identifies tables where **Snowflake Automatic Clustering** keeps re-clustering data but provides too little performance benefit to justify the cost.\
Automatic Clustering is a Snowflake service that continuously reorganizes a table's data according to its *clustering key* — the columns used to group related rows together. The service is billed in credits every time it re-clusters. When the key doesn't match how the table is queried, that spend is wasted.

This insight brings recommendations from the [Auto-Clustering Agent](/external-docs/fundamentals/our-features/auto-clustering-agent.md) into Waste Reduction, so you can review and track them alongside your other savings opportunities.

{% hint style="info" %}
**Required role:** [Viewer](/external-docs/fundamentals/settings/user-roles.md) or higher.

Any authenticated user can view these insights and mark them as Done. Applying the recommended change is done in Snowflake.
{% endhint %}

***

## How It Works

### Detection Logic

A table is flagged when all of the following are true:

1. **The Auto-Clustering Agent recommends removing clustering** — its analysis found that the clustering key gives little or no pruning benefit to the queries that run on the table.
2. **The table is still clustered** — it has a clustering key or auto-clustering enabled.
3. **Auto-clustering has a recent cost** — the table was re-clustered during the analysis window. Tables with no re-clustering spend are not flagged.

***

### Insight Details

Each insight includes:

* **Current clustering key** on the table.
* **Number of re-cluster events** and the **auto-clustering cost** during the analysis window.
* **Estimated annual savings** from removing auto-clustering. This figure matches the savings shown for the same table on the Auto-Clustering Agent page.
* The **Auto-Clustering Agent's analysis** for the table, explaining why removal is recommended.

***

## Remediation

1. Review the analysis in the insight to confirm that queries on the table won't slow down without clustering.
2. Run the SQL provided in the insight in a Snowflake worksheet, for example:

   ```sql
   ALTER TABLE "ANALYTICS"."SALES"."ORDERS" DROP CLUSTERING KEY;
   ```
3. Mark the insight as **Done** in Seemore.

The insight closes automatically once Seemore sees that the table is no longer clustered or has been dropped.

{% hint style="info" %}
Suspending re-clustering alone (`ALTER TABLE ... SUSPEND RECLUSTER`) keeps the clustering key on the table, so the insight stays open. Drop the clustering key to resolve it.
{% endhint %}

***

## Configuration

| Parameter       | Default | Description                                                                       |
| --------------- | ------- | --------------------------------------------------------------------------------- |
| Analysis window | 30 days | Period used to measure auto-clustering cost, annualized for the savings estimate. |

{% hint style="info" %}
The **Exclude Users from Usage** setting does **not** affect this insight. Remove Auto-Clustering is based on the Auto-Clustering Agent's analysis and Snowflake's auto-clustering billing.
{% endhint %}
