CREATE OPENFLOW RUNTIME¶
- See also:
ALTER OPENFLOW RUNTIME, DROP OPENFLOW RUNTIME, SHOW OPENFLOW RUNTIMES, DESCRIBE OPENFLOW RUNTIME
Creates a runtime in a gen 2 deployment.
Syntax¶
Required parameters¶
[ database.schema. ]nameSpecifies the identifier for the runtime. Use a fully qualified name or omit
database.schemato use the session default. For more information, see Identifier requirements.IN DEPLOYMENT deployment_nameGen 2 deployment that hosts this runtime.
NODE_TYPE = { SMALL | MEDIUM | LARGE }Node type. Cannot be changed after creation. Use
NODE_TYPE_TIERto resize within the same node type after creation.MIN_NODES = integerMinimum number of nodes (1–50).
MAX_NODES = integerMaximum number of nodes (1–50).
EXECUTE_AS_ROLE = roleRole connectors use when reading from and writing to Snowflake. See Create an execute-as role.
Optional parameters¶
NODE_TYPE_TIER = { S1 | S2 | S3 | M4 | M6 | L8 }Instance tier within the node type. The tier determines the CPU and heap memory available to each node. The tier must match the
NODE_TYPEvalue:S1,S2, andS3requireNODE_TYPE = SMALL;M4andM6requireNODE_TYPE = MEDIUM;L8requiresNODE_TYPE = LARGE.Tier Node type CPUs per node Heap per node S1SMALL 1 4 GB S2SMALL 2 8 GB S3SMALL 3 12 GB M4MEDIUM 4 16 GB M6MEDIUM 6 24 GB L8LARGE 8 33 GB You can change the tier within the same node type after creation using ALTER OPENFLOW RUNTIME … SET NODE_TYPE_TIER.
Default:
S1forSMALL,M4forMEDIUM,L8forLARGE.IF NOT EXISTSCreates the runtime only if it does not already exist. If the runtime already exists, the statement does nothing and returns a success message.
EXTERNAL_ACCESS_INTEGRATIONS = ( eai [ , ... ] )Snowflake deployments only. External access integrations that allow egress to external data sources.
Default: No value
DISPLAY_NAME = stringUI display name. If unset, the SQL
nameis shown in the Openflow UI.Default: No value
COMMENT = stringDefault: No value
Access control¶
Requires USAGE on the containing database, CREATE OPENFLOW RUNTIME on the target schema (or
schema ownership), and USAGE on the parent deployment.
Usage notes¶
- This command returns immediately. Runtime provisioning runs asynchronously and typically takes
3–5 minutes. Use
SYSTEM$WAIT_FOR_OPENFLOW_RUNTIME_STATUS
or
SYSTEM$WAIT_FOR_STABLE_OPENFLOW_RUNTIMES
to wait for the runtime to become
ACTIVE. - The optimal node count depends on your connector type and workload. See the setup topic for your connector for recommended values.