# Modify Snowflake warehouse
You can use the **Modify Snowflake warehouse** job entry to change the settings of an existing Snowflake virtual warehouse.
Modifying a warehouse is useful when usage patterns change throughout the day, week, month, or year. For example, you might scale up the warehouse during ETL processing to meet service-level agreements (SLAs), then scale it back down when the ETL completes.
For more information about working with Snowflake in PDI, see [PDI and Snowflake](/pdia-data-integration/extracting-data-into-pdi/pdi-and-snowflake-cp.md).
For more information about Snowflake warehouse settings, see the [Snowflake documentation](https://docs.snowflake.com/).
### General
* **Entry name**: Specify the unique name of the Modify Snowflake warehouse entry on the canvas. You can customize the name or leave it as the default.
### Options
The **Modify Snowflake warehouse** entry includes options for selecting a warehouse and changing warehouse attributes.
#### Database connection and warehouse
Specify the Snowflake database connection and identify the virtual warehouse you want to modify.
| Option | Description |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Database connection** | Select an existing Snowflake connection. If you do not have an existing connection, click New. If you need to modify an existing connection, click Edit.
Note: If timeout errors occur, see Snowflake timeout errors.
|
| **Use default warehouse** | Select to use the Snowflake default warehouse identified in the **Database connection**. |
| **Use an existing warehouse** | Select to use a warehouse other than the default one. Choose the warehouse name from the list. |
#### Warehouse settings
You can resize a warehouse at any time, even while it is running.
The **Auto suspend (in seconds)** setting helps ensure that an inactive warehouse stops consuming credits. The **Auto resume warehouse** setting controls whether the warehouse starts automatically when needed.
| Option | Description |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Warehouse size** | Select a size for this virtual warehouse:
- X-Small (default)
- Small
- Medium
- Large
- X-Large
- 2X-Large
- 3X-Large
- 4X-Large
Important: The size affects the number of servers in each cluster and the number of credits consumed while the warehouse is running.
|
| **Scaling policy** | Select the policy for automatically starting and shutting down clusters in a multi-cluster warehouse running in auto-scale mode:
|
| **Auto suspend (in seconds)** | Specify the time (in seconds) for the warehouse to auto-suspend when it becomes inactive. The default is 600 seconds (10 minutes).
You must specify a value of 60 or greater.
Important: If you leave this option blank, the warehouse never suspends. Leave this option blank only if your workload requires a continually running warehouse.
|
| **Resource monitor** | Select an existing resource monitor to assign to this warehouse. The default is blank (no monitor).
Note: A resource monitor is a permissions-based control that governs monthly credits used by this warehouse and any other warehouses that share the monitor.
|
| **Auto resume warehouse** | Specify whether to automatically resume the warehouse when a SQL statement is submitted.
- Cleared (default): the warehouse resumes only when you use the Start Snowflake warehouse job entry.
- Selected: the warehouse resumes automatically when a new query is submitted.
|
#### Cluster settings
The minimum and maximum cluster settings work together:
* If the minimum and maximum cluster count are the same, the warehouse runs in **Maximized** mode.
* If the minimum cluster count is less than the maximum cluster count, the warehouse runs in **Auto-scale** mode.
| Option | Description |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Minimum cluster count** | Select the minimum number of server clusters. Valid values are 1 to 10. The default is 1. This value must be less than or equal to **Maximum cluster count**. |
| **Maximum cluster count** | Select the maximum number of server clusters. Valid values are 1 to 10. The default is 1. Higher values require Snowflake Enterprise Edition. |
#### Activity settings
This setting controls what happens if the job requests a Snowflake warehouse that does not exist.
| Option | Description |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Fail if warehouse doesn't exist** | Specify how the job should behave if the requested warehouse does not exist:
- Selected (default): fail the job.
- Cleared: continue the job and move to the next entry.
|
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.pentaho.com/pdia-data-integration/pdi-job-entries-reference-overview/modify-warehouse-pdi-job-entry.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.