Snowflake Virtual Warehouses: 18%

On what is the billing for a virtual warehouse based?

• The average number of virtual servers used by query tasks per minute

• The number of query tasks running on the virtual warehouse multiplied by the number of
seconds with a minimum of 60 seconds

• The number of virtual servers used during a query multiplied by the number of seconds, with a
minimum of 60 seconds

• *The number of seconds the virtual warehouse is running multiplied by the number of virtual
servers in the cluster with a minimum of 60 seconds

• The time the virtual warehouse is running a query calculated by the second, with a minimum of
60 seconds

What happens if you increase the size of a warehouse while queries are running?

• The query is canceled, the virtual warehouse is resized and the query is started from the
beginning.

• The query is paused, the virtual warehouse is resized and the query is restarted.

• The virtual warehouse cancels the current query and stops the virtual warehouse, once the
virtual warehouse is stopped, it is resized and restarted. After it has restarted, the query is
resubmitted.

• The warehouse size is increased immediately, but any currently-running queries will keep
running at the old size until they complete.

• If the virtual warehouse size is increased, the query continues running in the current virtual
servers while the warehouse adds the additional virtual servers. If the virtual warehouse size is
decreased, the query tasks are moved to what will be the remaining virtual servers and the
other servers are removed from the virtual warehouses.
If a multi-cluster warehouse is using an economy scaling policy, how long will queries back up in the
queue before another cluster is started?

• 8 minutes

• 4 minutes

• It will start the next cluster as soon as the queue starts backing up

• 2 minutes

• 6 minutes

what is the benefit of a warehouse using an economy scaling policy?

• It matches the size of the cluster to the query when it starts a new cluster.

• Clusters will stop immediately when no longer needed and stop using credits.

• The multi-cluster will start all clusters whenever a query is submitted to provide maximum
resources to reduce the queue as fast as possible and then shut down.

• The number of credits is based on the number of virtual servers needed to run a query and idle
virtual servers are not charged.

• It keeps the running clusters busier and it does not start a new cluster immediately when a
query is queued, in case the queuing is an anomaly rather than the start of an upward usage
trend.