A.Database stage

B.External stage

C.Table stage

D.User stage

A.Yes. became the new compute resource will no longer have access to the cache encryption key

B.Possibly, if the warehouse is resized to a smaller size and the cache no longer fits.

C.Yes. because the compute resource is replaced in its entirety with a new compute resource.

D.No. because the size of the cache is independent from the warehouse size

A.Load files that are approximately 25 MB or smaller.

B.Remove all dates and timestamps.

C.Load files that are approximately 100-250 MB (or larger)

D.Avoid using embedded characters such as commas for numeric data types

E.Remove semi-structured data types

A.Cluster keys

B.Time Travel

C.Fail-safe

D.Cloning

A.Querying (select) the size of the stream content would help determine the warehouse size. For example, if querying large stream content, use a larger warehouse size

B.Since task infrastructure is based on running the task body on schedule, it's recommended to configure the virtual warehouse for automatic concurrency handling using Multi-cluster warehouse (MCW) to match the task schedule

C.Root task may be executed concurrently (i.e. multiple instances), it is recommended to leave some margins in the execution window to avoid missing instances of execution

D.If using the stored procedure to execute multiple SQL statements, it's best to test run the stored procedure separately to size the compute resource first