{"type":"doc","content":[{"type":"paragraph","content":[{"text":"This page provides general guidelines on how to set up Snowflake Storage to work with Storage Management.","type":"text"}]},{"type":"extension","attrs":{"layout":"default","extensionType":"com.atlassian.confluence.macro.core","extensionKey":"toc","parameters":{"macroParams":{},"macroMetadata":{"macroId":{"value":"e4f72a59-b656-4e34-ba25-982c06e69da2"},"schemaVersion":{"value":"1"},"title":"Table of Contents"}},"localId":"fbf47212-6437-469f-8c4b-08db0ffb01d4"}},{"type":"paragraph"},{"type":"panel","attrs":{"panelType":"warning"},"content":[{"type":"paragraph","content":[{"text":"With the introduction of ","type":"text"},{"text":"Snowpipe Streaming","type":"text","marks":[{"type":"strong"},{"type":"link","attrs":{"href":"https://docs.snowflake.com/en/user-guide/data-load-snowpipe-streaming-overview"}}]},{"text":", the connection setup procedure is slightly different compared to the previous ","type":"text"},{"text":"Batch Load","type":"text","marks":[{"type":"strong"}]},{"text":" data replication method.","type":"text"},{"type":"hardBreak"},{"text":"The crucial differentiator is whether ","type":"text"},{"text":"Snowflake Ingest SDK","type":"text","marks":[{"type":"strong"}]},{"text":" is to be used or not. Because this SDK contains an internal driver manager conflicting with the default one used by SNP Java Connector, the ","type":"text"},{"text":"Snowpipe Streaming needs to be fully separated from any other connections","type":"text","marks":[{"type":"strong"}]},{"text":".","type":"text"},{"type":"hardBreak"},{"text":"This is further explained in the instructions below.","type":"text"}]}]},{"type":"heading","attrs":{"level":1},"content":[{"text":"1. General prerequisites","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"1.1 Network Connectivity","type":"text"}]},{"type":"paragraph","content":[{"text":"To enable communication of SAP systems with the Snowflake host, the following host/ports need to be reachable from the SAP system:","type":"text"}]},{"type":"table","attrs":{"layout":"default","width":1800.0,"localId":"5b45e880-4b4c-4247-9b65-350db051f8fa"},"content":[{"type":"tableRow","content":[{"type":"tableHeader","attrs":{"colspan":1,"background":"#f0f0f0","rowspan":1,"colwidth":[80.0]},"content":[{"type":"paragraph","content":[{"text":"Port","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableHeader","attrs":{"colspan":1,"rowspan":1,"colwidth":[680.0]},"content":[{"type":"paragraph","content":[{"text":"Address","type":"text","marks":[{"type":"strong"}]}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[80.0]},"content":[{"type":"paragraph","content":[{"text":"443","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[680.0]},"content":[{"type":"paragraph","content":[{"text":"...snowflakecomputing.com","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[80.0]},"content":[{"type":"paragraph","content":[{"text":"443","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[680.0]},"content":[{"type":"paragraph","content":[{"text":"ocsp.snowflakecomputing.com","type":"text","marks":[{"type":"link","attrs":{"href":"http://ocsp.snowflakecomputing.com"}}]}]}]}]}]},{"type":"panel","attrs":{"panelType":"info"},"content":[{"type":"paragraph","content":[{"text":"If your Snowflake account is hosted in a particular cloud environment like AWS or MS Azure, make sure their respective domains are reachable from the SAP system (e.g. *.amazonaws.com, *.windows.net); port 443.","type":"text"},{"type":"hardBreak"},{"text":"This is needed for file upload to the Snowflake internal staging area if the ","type":"text"},{"text":"Batch Load","type":"text","marks":[{"type":"strong"}]},{"text":" data replication method is used.","type":"text"},{"type":"hardBreak"},{"text":"There is an automatic redirect happening during the PUT operation when transferring data to the Snowflake internal stage, which goes to the respective vendor’s file service (example: ","type":"text"},{"text":"customer-stage.s3.us-east-2.amazonaws.com","type":"text","marks":[{"type":"link","attrs":{"href":"http://customer-stage.s3.us-east-2.amazonaws.com"}}]},{"text":").","type":"text"}]},{"type":"paragraph","content":[{"text":"In case of connectivity problems, Snowflake offers SnowCD utility to check connectivity towards Snowflake service endpoints possibly involved in the communication: ","type":"text"},{"type":"inlineCard","attrs":{"url":"https://docs.snowflake.com/en/user-guide/snowcd.html#"}},{"text":" ","type":"text"}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"1.2 Warehouse and Database","type":"text"}]},{"type":"paragraph","content":[{"text":"Snowflake warehouse and database must already exist.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"1.3 Snowflake user","type":"text"}]},{"type":"paragraph","content":[{"text":"Snowflake technical users must be created with full privileges on the chosen Snowflake DB schema.","type":"text"},{"type":"hardBreak"},{"text":"The recommended privilege for the Snowflake technical user is OWNERSHIP of the Snowflake database.","type":"text"},{"type":"hardBreak"},{"text":"In case ownership of the database cannot be assigned to the technical user, minimal requirements are the following:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"sql"},"content":[{"text":"GRANT ALL ON DATABASE TO ROLE \nGRANT USAGE ON WAREHOUSE TO ROLE \nGRANT ALL ON SCHEMA TO ROLE ","type":"text"}]},{"type":"paragraph","content":[{"text":"There should be a one-to-one relation between Snowflake schemas and every SAP system connected, ensuring replicated data isolation.","type":"text"}]},{"type":"heading","attrs":{"level":1},"content":[{"text":"2. OS prerequisites (On SAP host)","type":"text"}]},{"type":"paragraph","content":[{"text":"This group of requirements relates to the operating systems underlying the SAP system with all its application servers.","type":"text"},{"type":"hardBreak"},{"text":"SNP products (e.g. SNP Glue™, SNP OutBoard™ Data Tiering) have been developed and tested in the SUSE Linux environment and Windows Server 2012.","type":"text"},{"type":"hardBreak"},{"text":"However, by design, they are not limited by the choice of an operating system, if the requirements listed in this guide are met.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"2.1 OS directory with JDBC Driver and/or Snowflake Ingest SDK","type":"text"}]},{"type":"paragraph","content":[{"text":"JDBC protocol is used to connect to Snowflake. Snowflake JDBC driver needs to be manually copied to the operating system and accessible to the Java connector.","type":"text"},{"type":"hardBreak"},{"text":"Download Snowflake JDBC driver","type":"text","marks":[{"type":"link","attrs":{"href":"https://docs.snowflake.com/en/user-guide/jdbc-download.html#downloading-the-driver"}}]},{"text":". ","type":"text"},{"text":"The latest version of the Snowflake JDBC driver ","type":"text","marks":[{"type":"strong"}]},{"text":"is recommended, ","type":"text"},{"text":"except for the Snowpipe Streaming","type":"text","marks":[{"type":"strong"}]},{"text":" storage connection - the streaming replication method currently requires JDBC driver version ","type":"text"},{"text":"3.13.30 to 3.14.5","type":"text","marks":[{"type":"link","attrs":{"href":"https://repo1.maven.org/maven2/net/snowflake/snowflake-jdbc/3.14.5/snowflake-jdbc-3.14.5.jar"}}]},{"text":" in combination with ","type":"text"},{"text":"snowflake-ingest-sdk-2.0.x.jar","type":"text","marks":[{"type":"link","attrs":{"href":"https://repo1.maven.org/maven2/net/snowflake/snowflake-ingest-sdk/2.0.4/snowflake-ingest-sdk-2.0.4.jar"}}]},{"text":".","type":"text"},{"type":"hardBreak"},{"text":"It is recommended to store the drivers in a filesystem shared between the application servers, organized in sub-directories to avoid possible conflicts (some customers connect to multiple different platforms/services). Important information is that while the path to the driver directory is defined in the storage connection (SAP GUI), the drivers themselves are loaded by the Java connector component.","type":"text"}]},{"type":"paragraph","content":[{"text":"Sample directory with the JDBC driver for standard ","type":"text"},{"text":"Batch Load","type":"text","marks":[{"type":"strong"}]},{"text":" method:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"shell"},"content":[{"text":"$ ls -l /sapmnt//drivers/snowflake\n-rwxr-xr-x 1 adm root 69376363 Jan 15 09:45 snowflake-jdbc-3.14.5.jar","type":"text"}]},{"type":"paragraph","content":[{"text":"Sample directory with both JDBC driver and Ingest SDK for ","type":"text"},{"text":"Snowpipe Streaming","type":"text","marks":[{"type":"strong"}]},{"text":":","type":"text"}]},{"type":"codeBlock","attrs":{"language":"shell"},"content":[{"text":"$ ls -l /sapmnt//drivers/snowflake_streaming\n-rw-r--r-- 1 adm sapsys 52768695 Dec 1 16:31 snowflake-ingest-sdk-2.0.4.jar\n-rw-r--r-- 1 adm sapsys 33471655 Jan 31 11:53 snowflake-jdbc-3.13.34.jar","type":"text"}]},{"type":"paragraph","content":[{"text":"Set its ownership and permissions appropriately to ","type":"text"},{"text":"adm[:sapsys]","type":"text","marks":[{"type":"code"}]},{"text":".","type":"text"}]},{"type":"panel","attrs":{"panelType":"warning"},"content":[{"type":"paragraph","content":[{"text":"For compatibility with the SNP Java connector, the Snowflake JDBC driver filename must begin with the prefix ","type":"text"},{"text":"snowflake-jdbc","type":"text","marks":[{"type":"strong"}]},{"text":". If there are multiple versions of the Snowflake driver present, the latest version will be utilized. It is advisable to keep only one version of the JDBC driver within the Snowflake driver directory. ","type":"text"}]},{"type":"paragraph","content":[{"text":"The Snowflake Ingest SDK JAR filename must begin with the prefix ","type":"text"},{"text":"snowflake-ingest","type":"text","marks":[{"type":"strong"}]},{"text":". Similarly, if there are multiple versions of the Snowflake Ingest SDK available, the most recently added version will be used. It is recommended to keep only one version of both the JDBC driver and the Snowflake Ingest SDK within the Snowflake streaming driver directory.","type":"text"}]}]},{"type":"panel","attrs":{"panelType":"info"},"content":[{"type":"paragraph","content":[{"text":"There was an issue with the SSL handshake in older versions of the driver (3.13.x), this issue was fixed in the ","type":"text"},{"text":"snow-jdbc-3.13.21","type":"text","marks":[{"type":"link","attrs":{"href":"https://repo1.maven.org/maven2/net/snowflake/snowflake-jdbc/3.13.21/snowflake-jdbc-3.13.21.jar"}}]},{"text":" version.","type":"text"}]}]},{"type":"heading","attrs":{"level":1},"content":[{"text":"3. SAP configuration","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"3.1 JAVA connector","type":"text"}]},{"type":"paragraph","content":[{"text":"Java connector is a critical middle-ware component. Follow the steps in ","type":"text"},{"text":"Java Connector Setup","type":"text","marks":[{"type":"link","attrs":{"href":"https://datavard.atlassian.net/wiki/spaces/DATAVARD/pages/4510357085/SM-2402+Java+Connector+Setup"}}]},{"text":" to set it up/upgrade to a new version before you continue. ","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":1002,"widthType":"pixel"},"content":[{"type":"media","attrs":{"width":1060,"id":"57074c32-5c6f-472d-8b83-d0f51d0ffed3","collection":"contentId-4510356149","type":"file","height":337}}]},{"type":"paragraph","content":[{"text":"The ","type":"text"},{"text":"Java runtime environment","type":"text","marks":[{"type":"link","attrs":{"href":"https://datavard.atlassian.net/wiki/spaces/DATAVARD/pages/4510357085/SM-2402+Java+Connector+Setup#Java-runtime-environment"}}]},{"text":" is narrowed due to Snowflake JDBC driver requirement - it must be installed in a 64-bit environment and requires Java 1.8 (or higher), link to the official page: ","type":"text"},{"type":"inlineCard","attrs":{"url":"https://docs.snowflake.com/en/user-guide/jdbc.html"}},{"text":".","type":"text"}]},{"type":"panel","attrs":{"panelType":"warning"},"content":[{"type":"paragraph","content":[{"text":"In the case of JCo running on JDK 16, add a custom argument in the Advanced tab → Additional java starting arguments: ","type":"text"},{"text":"-Djdk.module.illegalAccess=permit","type":"text","marks":[{"type":"code"}]},{"type":"hardBreak"},{"text":"JDK 16 introduced strong encapsulation of JDK internals (see the documentation ","type":"text"},{"type":"inlineCard","attrs":{"url":"https://www.oracle.com/java/technologies/javase/16-all-relnotes.html#JDK-8256299"}},{"text":" ) that caused problems in combination with the Snowflake JDBC driver.","type":"text"},{"type":"hardBreak"},{"text":"In JDK 17 option ","type":"text"},{"text":"-Djdk.module.illegalAccess=permit","type":"text","marks":[{"type":"code"}]},{"text":" does not work anymore and is therefore unusable for connection using the Snowflake JDBC driver (for more information see ","type":"text"},{"type":"inlineCard","attrs":{"url":"https://www.oracle.com/java/technologies/javase/17all-relnotes.html"}},{"text":" ).","type":"text"}]}]},{"type":"panel","attrs":{"panelType":"warning"},"content":[{"type":"paragraph","content":[{"text":"In cases where the user wants to utilize ","type":"text"},{"text":"both the Snowflake Batch Load","type":"text","marks":[{"type":"strong"}]},{"text":" connection ","type":"text"},{"text":"and Snowpipe Streaming ","type":"text","marks":[{"type":"strong"}]},{"text":"connections simultaneously, it is required to ","type":"text"},{"text":"set up separate Java Connector instances","type":"text","marks":[{"type":"strong"}]},{"text":" for each replication method.","type":"text"}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"3.2 Storage Management Setup","type":"text"}]},{"type":"paragraph","content":[{"text":"The final step in SAP & Snowflake connectivity is the creation of appropriate storage connections in transaction ","type":"text"},{"text":"/DVD/SM_SETUP","type":"text","marks":[{"type":"code"}]},{"text":" ","type":"text"}]},{"type":"paragraph","content":[{"text":"For the ","type":"text"},{"text":"Batch Load ","type":"text","marks":[{"type":"strong"}]},{"text":"replication method ","type":"text"},{"text":"SNOW_STAGE","type":"text","marks":[{"type":"strong"}]},{"text":" and ","type":"text"},{"text":"SNOWFLAKE","type":"text","marks":[{"type":"strong"}]},{"text":" type connections need to be configured (the first one for data file upload, the second for SQL communication with Snowflake API):","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"3.2.1 Snowflake Stage (SNOW_STAGE)","type":"text"}]},{"type":"paragraph","content":[{"text":"Binary storage points to the Internal Stage of the Snowflake user. It is used for data transfer leveraging the extended functionality of the Snowflake JDBC driver. ","type":"text"}]},{"type":"paragraph","content":[{"text":"Storage ID","type":"text","marks":[{"type":"code"}]},{"text":": Logical name of the storage connection.","type":"text"},{"type":"hardBreak"},{"text":"Storage type","type":"text","marks":[{"type":"code"}]},{"text":": SNOW_STAGE (Snowflake internal stage).","type":"text"},{"type":"hardBreak"},{"text":"Java connector RFC","type":"text","marks":[{"type":"code"}]},{"text":": TCP/IP RFC destination used for communication with Java connector.","type":"text"},{"type":"hardBreak"},{"text":"Account name","type":"text","marks":[{"type":"code"}]},{"text":": Name of the Snowflake account without ","type":"text"},{"text":".snowflakecomputing.com","type":"text","marks":[{"type":"code"}]},{"text":" domain, in the format: .. (more information can be found in ","type":"text"},{"text":"Snowflake account name doc","type":"text","marks":[{"type":"link","attrs":{"href":"https://docs.snowflake.com/en/user-guide/connecting.html#your-snowflake-account-name"}}]},{"text":").","type":"text"},{"type":"hardBreak"},{"text":"User role","type":"text","marks":[{"type":"code"}]},{"text":": The user's role used for data insertion.","type":"text"},{"type":"hardBreak"},{"text":"JAVA Call Repeat","type":"text","marks":[{"type":"code"}]},{"text":": Number of times failed calls should be retried.","type":"text"},{"type":"hardBreak"},{"text":"Repeat delay (seconds","type":"text","marks":[{"type":"code"}]},{"text":": Delay between retried calls.","type":"text"},{"type":"hardBreak"},{"text":"Driver path","type":"text","marks":[{"type":"code"}]},{"text":": Absolute path to the directory containing the Snowflake JDBC driver.","type":"text"},{"type":"hardBreak"},{"text":"NOTE: In previous versions of Storage Management, SAP logical file of type DIR (directory) was used. This is now automatically converted to a physical path.","type":"text"},{"type":"hardBreak"},{"text":"Connection pool size","type":"text","marks":[{"type":"code"}]},{"text":": Number of connections that can be kept open in the pool, reducing resource-expensive establishment of JDBC connections.","type":"text"},{"type":"hardBreak"},{"text":"Username","type":"text","marks":[{"type":"code"}]},{"text":": Snowflake user.","type":"text"},{"type":"hardBreak"},{"text":"Password","type":"text","marks":[{"type":"code"}]},{"text":": User password.","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":780,"widthType":"pixel"},"content":[{"type":"media","attrs":{"width":1106,"id":"8cafabaf-d2f5-4508-9025-a11917fd996b","collection":"contentId-4510356149","type":"file","height":713}}]},{"type":"paragraph","content":[{"text":"If Key Pair authentication is established according to ","type":"text"},{"type":"inlineCard","attrs":{"url":"https://docs.snowflake.com/en/user-guide/key-pair-auth.html#key-pair-authentication-key-pair-rotation"}},{"text":", it can be configured with or without a passphrase as follows:","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":780,"widthType":"pixel"},"content":[{"type":"media","attrs":{"width":1107,"id":"ea90a672-3d4a-43a9-b541-7797f5de1d9b","collection":"contentId-4510356149","type":"file","height":274}}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"3.2.2 Snowflake Storage (SNOWFLAKE)","type":"text"}]},{"type":"paragraph","content":[{"text":"Transparent storage pointing to Snowflake Database. For sending SQL command data use the Snowflake JDBC driver. ","type":"text"}]},{"type":"paragraph","content":[{"text":"Storage ID","type":"text","marks":[{"type":"code"}]},{"text":": Logical name of the storage connection.","type":"text"},{"type":"hardBreak"},{"text":"Storage type","type":"text","marks":[{"type":"code"}]},{"text":": SNOWFLAKE (Snowflake transparent storage).","type":"text"},{"type":"hardBreak"},{"text":"Referenced storage","type":"text","marks":[{"type":"code"}]},{"text":": Storage ID of Snowflake stage area for temporary file upload/download.","type":"text"},{"type":"hardBreak"},{"text":"Java connector RFC","type":"text","marks":[{"type":"code"}]},{"text":": RFC Destination used for communication with JCo.","type":"text"},{"type":"hardBreak"},{"text":"Account name","type":"text","marks":[{"type":"code"}]},{"text":": .. (more information can be found in ","type":"text"},{"text":"Snowflake account name doc","type":"text","marks":[{"type":"link","attrs":{"href":"https://docs.snowflake.com/en/user-guide/connecting.html#your-snowflake-account-name"}}]},{"text":").","type":"text"},{"type":"hardBreak"},{"text":"Warehouse","type":"text","marks":[{"type":"code"}]},{"text":": Optional parameter, you can select the existing warehouse in the Snowflake account to be used.","type":"text"},{"type":"hardBreak"},{"text":"Database","type":"text","marks":[{"type":"code"}]},{"text":": Name of an existing database in Snowflake.","type":"text"},{"type":"hardBreak"},{"text":"Database schema","type":"text","marks":[{"type":"code"}]},{"text":": Name of an existing database schema in Snowflake.","type":"text"},{"type":"hardBreak"},{"text":"User role","type":"text","marks":[{"type":"code"}]},{"text":": The user's role used for data insertion.","type":"text"},{"type":"hardBreak"},{"text":"Driver path","type":"text","marks":[{"type":"code"}]},{"text":": Snowflake driver directory.","type":"text"},{"type":"hardBreak"},{"text":"Hints","type":"text","marks":[{"type":"code"}]},{"text":": Additional string added to connection string when JDBC driver establishes a connection.","type":"text"},{"type":"hardBreak"},{"text":"Connection pool size","type":"text","marks":[{"type":"code"}]},{"text":": Number of connections that can be kept open in the pool, reducing resource-expensive establishment of JDBC connections.","type":"text"},{"type":"hardBreak"},{"text":"Table name prefix","type":"text","marks":[{"type":"code"}]},{"text":": Optional text value for naming prefix of all Glue tables created within this storage.","type":"text"},{"type":"hardBreak"},{"text":"Use Transient tables","type":"text","marks":[{"type":"code"}]},{"text":": When enabled, only transient tables will be created on the storage.","type":"text"},{"type":"hardBreak"},{"text":"Use Snowflake App for data merge:","type":"text","marks":[{"type":"code"}]},{"text":" When enabled, the ","type":"text"},{"text":"SNP Native app","type":"text","marks":[{"type":"strong"},{"type":"link","attrs":{"href":"https://datavard.atlassian.net/wiki/spaces/DATAVARD/pages/4510331597/Glue+2402+Snowflake+Native+App"}}]},{"text":" will be used. ","type":"text"},{"type":"hardBreak"},{"text":"Snowflake App name","type":"text","marks":[{"type":"code"}]},{"text":": Name of the existing Snowflake native App to be used.","type":"text"},{"type":"hardBreak"},{"text":"Wrap values in staged CSV files","type":"text","marks":[{"type":"code"}]},{"text":": Depending on table content, it may be necessary to encapsulate field values to avoid errors during INSERT into the Snowflake table from staging CSV files.","type":"text"},{"type":"hardBreak"},{"text":"Data delivery guarantee","type":"text","marks":[{"type":"code"}]},{"text":": Data transfer behavior. More information can be found in the chapter ","type":"text"},{"text":"Data Delivery Guarantee","type":"text","marks":[{"type":"link","attrs":{"href":"https://datavard.atlassian.net/wiki/spaces/DATAVARD/pages/4510357919/SM-2402+Data+Delivery+Guarantee"}}]},{"text":".","type":"text"}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":"For the ","type":"text"},{"text":"Snowpipe Streaming","type":"text","marks":[{"type":"strong"}]},{"text":" replication method only one ","type":"text"},{"text":"SNOWSTREAM","type":"text","marks":[{"type":"strong"}]},{"text":" type connection is sufficient:","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"3.2.3 Snowpipe Streaming Storage (SNOWSTREAM)","type":"text"}]},{"type":"paragraph","content":[{"text":"Transparent storage pointing to Snowflake Database. For sending SQL commands, data uses the Snowflake JDBC driver. To insert data into the Snowflake database ","type":"text"},{"text":"Snowflake Ingest SDK","type":"text","marks":[{"type":"strong"}]},{"text":" is used. For more information about Snowpipe Streaming, requirements, limitations, and configuration visit the official ","type":"text"},{"text":"Snowpipe Streaming documentation","type":"text","marks":[{"type":"link","attrs":{"href":"https://docs.snowflake.com/en/user-guide/data-load-snowpipe-streaming-overview"}}]},{"text":". ","type":"text"}]},{"type":"panel","attrs":{"panelType":"warning"},"content":[{"type":"paragraph","content":[{"text":"Snowpipe Streaming connection supports only the Key Pair authentication method, please see ","type":"text"},{"type":"inlineCard","attrs":{"url":"https://docs.snowflake.com/en/user-guide/key-pair-auth.html#key-pair-authentication-key-pair-rotation"}},{"text":" for more information.","type":"text"}]}]},{"type":"paragraph","marks":[{"type":"indentation","attrs":{"level":1}}],"content":[{"text":"Storage ID","type":"text","marks":[{"type":"code"}]},{"text":": Logical name of the storage connection.","type":"text"},{"type":"hardBreak"},{"text":"Storage type","type":"text","marks":[{"type":"code"}]},{"text":": SNOWSTREAM (Snowflake transparent storage - Streaming).","type":"text"},{"type":"hardBreak"},{"text":"Java connector RFC","type":"text","marks":[{"type":"code"}]},{"text":": RFC Destination used for communication with JCo.","type":"text"},{"type":"hardBreak"},{"text":"Account name","type":"text","marks":[{"type":"code"}]},{"text":": .. (more information can be found in ","type":"text"},{"text":"Snowflake account name doc","type":"text","marks":[{"type":"link","attrs":{"href":"https://docs.snowflake.com/en/user-guide/connecting.html#your-snowflake-account-name"}}]},{"text":").","type":"text"},{"type":"hardBreak"},{"text":"Warehouse","type":"text","marks":[{"type":"code"}]},{"text":": Optional parameter, you can select the existing warehouse in the Snowflake account to be used.","type":"text"},{"type":"hardBreak"},{"text":"Database","type":"text","marks":[{"type":"code"}]},{"text":": Name of an existing database in Snowflake.","type":"text"},{"type":"hardBreak"},{"text":"Database schema","type":"text","marks":[{"type":"code"}]},{"text":": Name of an existing database schema in Snowflake.","type":"text"},{"type":"hardBreak"},{"text":"User role","type":"text","marks":[{"type":"code"}]},{"text":": The user's role used for data insertion.","type":"text"},{"type":"hardBreak"},{"text":"Driver path","type":"text","marks":[{"type":"code"}]},{"text":": Snowflake driver directory. It’s required to include the ","type":"text"},{"text":"Snowflake Ingest SDK","type":"text","marks":[{"type":"strong"}]},{"text":" jar file in this directory. The SDK is available for download from the ","type":"text"},{"text":"Snowflake Maven Central Repository","type":"text","marks":[{"type":"link","attrs":{"href":"https://mvnrepository.com/artifact/net.snowflake/snowflake-ingest-sdk"}}]},{"text":".","type":"text"},{"type":"hardBreak"},{"text":"Hints","type":"text","marks":[{"type":"code"}]},{"text":": Additional string added to connection string when JDBC driver establishes a connection.","type":"text"},{"type":"hardBreak"},{"text":"Connection pool size","type":"text","marks":[{"type":"code"}]},{"text":": Number of connections that can be kept open in the pool, reducing resource-expensive establishment of JDBC connections.","type":"text"},{"type":"hardBreak"},{"text":"Username","type":"text","marks":[{"type":"code"}]},{"text":": Snowflake user.","type":"text"},{"type":"hardBreak"},{"text":"Private Key file location:","type":"text","marks":[{"type":"code"}]},{"text":" Path to Private Key file.","type":"text"},{"type":"hardBreak"},{"text":"Private Key Encrypted:","type":"text","marks":[{"type":"code"}]},{"text":" When enabled, a Password input field will be displayed.","type":"text"},{"type":"hardBreak"},{"text":"Password:","type":"text","marks":[{"type":"code"}]},{"text":" Password to Private key.","type":"text"},{"type":"hardBreak"},{"text":"Use Snowflake App for data merge:","type":"text","marks":[{"type":"code"}]},{"text":" When enabled, the ","type":"text"},{"text":"SNP Native app","type":"text","marks":[{"type":"strong"},{"type":"link","attrs":{"href":"https://datavard.atlassian.net/wiki/spaces/DATAVARD/pages/4510331597/Glue+2402+Snowflake+Native+App"}}]},{"text":" will be used. ","type":"text"},{"type":"hardBreak"},{"text":"Snowflake App name","type":"text","marks":[{"type":"code"}]},{"text":": Name of the existing Snowflake native App to be used.","type":"text"},{"type":"hardBreak"},{"text":"Table name prefix","type":"text","marks":[{"type":"code"}]},{"text":": Optional text value for naming prefix of all tables created within this storage.","type":"text"},{"type":"hardBreak"},{"text":"Data delivery guarantee","type":"text","marks":[{"type":"code"}]},{"text":": Data transfer behavior. More information can be found in the chapter ","type":"text"}]},{"type":"panel","attrs":{"panelType":"info"},"content":[{"type":"paragraph","content":[{"text":"If the data contains invalid ","type":"text"},{"text":"date","type":"text","marks":[{"type":"strong"}]},{"text":" values, these are checked during the extraction. The inconsistent dates will be set to null so the replication can continue.","type":"text"}]}]}],"version":1}

Browser not supported