%3CLINGO-SUB%20id%3D%22lingo-sub-1447370%22%20slang%3D%22en-US%22%3EADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1447370%22%20slang%3D%22en-US%22%3E%3CP%20data-unlink%3D%22true%22%3EAzure%20Data%20Factory%20provides%2090%2B%20built-in%20connectors%26nbsp%3Ballowing%20you%20to%20easily%20integrate%20with%20various%20data%20stores%20regardless%20of%20variety%20of%20volume%2C%20whether%20they%20are%20on%20premises%20or%20in%20the%20cloud.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20glad%20to%20share%20that%20ADF%20newly%20added%20support%20for%20%3CSTRONG%3ESnowflake%20connector%3C%2FSTRONG%3E%20with%20the%20following%20capabilities%20to%20fulfill%20your%20Snowflake%20data%20integration%20need%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIngest%20data%20from%20Snowflake%20into%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fdata-factory%2Fcopy-activity-overview%23supported-data-stores-and-formats%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eany%20supported%20sinks%3C%2FA%3E%20(e.g.%20data%20lake)%20using%20Copy%20activity%2C%20which%20utilizes%20Snowflake%E2%80%99s%20%3CA%20href%3D%22https%3A%2F%2Fdocs.snowflake.com%2Fen%2Fsql-reference%2Fsql%2Fcopy-into-location.html%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECOPY%20into%20%3CLOCATION%3E%3C%2FLOCATION%3E%3C%2FA%3E%20command%20to%20achieve%20the%20best%20performance%3B%3C%2FLI%3E%0A%3CLI%3ELook%20up%20data%20from%20Snowflake%20for%20ADF%20control%20flow%20consumption%20using%20Lookup%20activity%3B%3C%2FLI%3E%0A%3CLI%3ELoad%20data%20into%20Snowflake%20from%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fdata-factory%2Fcopy-activity-overview%23supported-data-stores-and-formats%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E90%20plus%20supported%20sources%3C%2FA%3E%20using%20Copy%20activity%2C%20which%20takes%20advantage%20of%20Snowflake%E2%80%99s%20%3CA%20href%3D%22https%3A%2F%2Fdocs.snowflake.com%2Fen%2Fsql-reference%2Fsql%2Fcopy-into-table.html%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECOPY%20into%20%3C%2FA%3E%3CTABLE%3E%20command%20to%20achieve%20the%20best%20performance.%0A%0A%3CP%3EYou%20can%20now%20find%20Snowflake%20connector%20from%20ADF%20connector%20gallery%20UI.%20Learn%20more%20from%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdata-factory%2Fconnector-snowflake%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESnowflake%20connector%20documentation%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22SnowflakeConnector.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F197157i3404F0C02B67BCC7%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22SnowflakeConnector.png%22%20alt%3D%22SnowflakeConnector.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EUpcoming%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3ENext%2C%20we%20plan%20to%20enable%20the%20following%20to%20further%20enrich%20the%20ADF-Snowflake%20integration%20capabilities.%20Stay%20tuned!%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ELoad%20semi-structured%20data%20from%20JSON%20files%20into%20Snowflake%20VARIANT%20column%20using%20Copy%20activity%2C%20for%20data%20processing%20in%20Snowflake%20subsequently.%3C%2FLI%3E%0A%3CLI%3ESupport%20Snowflake%20in%20Mapping%20Data%20Flow%20as%20source%20and%20sink%20transformations%20to%20provide%20seamless%20ETL.%20Before%20it%E2%80%99s%20available%2C%20you%20can%20use%20Copy%20activity%20in%20conjunction%20of%20Data%20Flow%2C%20e.g.%20perform%20transformation%20using%20Data%20Flow%20on%20top%20of%20data%20lake%2C%20and%20use%20Copy%20activity%20to%20load%20data%20into%2Ffrom%20Snowflake.%3C%2FLI%3E%0A%3C%2FUL%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1447370%22%20slang%3D%22en-US%22%3E%3CP%3EAzure%20Data%20Factory%20provides%2090%2B%20built-in%20connectors%26nbsp%3Ballowing%20you%20to%20easily%20integrate%20with%20various%20data%20stores%20regardless%20of%20variety%20of%20volume%2C%20whether%20they%20are%20on%20premises%20or%20in%20the%20cloud.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1447370%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Data%20Factory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Data%20Integration%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3C%2FTABLE%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1449407%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1449407%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20one%20of%20our%20energy%20client(can't%20take%20the%20name%20for%20confidentiality)%20we%20found%20the%20performance%20of%20ADF%20when%20loading%20data%20into%20Snowflake%20was%20not%20great.%20Then%20raised%20a%20ticket%20to%20Microsoft%20and%20MS%20support%20team%20advised%20to%20use%20Matillion%20inside%20Azure.%20After%20that%20we%20found%20performance%20of%20data%20load%20been%20increased.%20It's%20around%203%2F4%20months%20old%20story.%20Does%20this%20still%20true%20for%20large%20volume%20of%20data%20load%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1450062%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1450062%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F407167%22%20target%3D%22_blank%22%3E%40avixorld%3C%2FA%3E%26nbsp%3Bthis%20Snowflake%20connector%20utilizes%20Snowflake's%20most%20recommended%20and%20performant%20way%20to%20load%20data%20and%20can%20scale%20for%20large%20volume%20of%20data.%20Not%20sure%20what%20exact%20mechanism%20your%20client%20used%20earlier.%20If%20any%20perf%20issue%20going%20forward%2C%20please%20keep%20raising%20support%20ticket%20and%20we'd%20love%20to%20look%20into%20the%20specific%20case.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1450987%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1450987%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20update%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F414697%22%20target%3D%22_blank%22%3E%40Linda_Wang%3C%2FA%3E%26nbsp%3B!!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20executing%20Snowflake%20stored%20procedure%20from%20Lookup%20activity%20and%20it%20succeeds%20at%20the%20database%20level%20but%20errors%20out%20in%20the%20UI%20-%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%7B%20%22errorCode%22%3A%20%222100%22%2C%20%22message%22%3A%20%22Failure%20happened%20on%20'Source'%20side.%20ErrorCode%3DUserErrorOdbcInvalidQueryString%2C'Type%3DMicrosoft.DataTransfer.Common.Shared.HybridDeliveryException%2CMessage%3DThe%20following%20ODBC%20Query%20is%20not%20valid%3A%20'call%20CDM.test1('c')'.%2CSource%3DMicrosoft.DataTransfer.Runtime.GenericOdbcConnectors%2C'%22%2C%20%22failureType%22%3A%20%22UserError%22%2C%20%22target%22%3A%20%22Lookup1%22%2C%20%22details%22%3A%20%5B%5D%20%7D%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Ea%20known%20issue%20%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1451633%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1451633%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20the%20update%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F414697%22%20target%3D%22_blank%22%3E%40Linda_Wang%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20let%20us%20know%20if%20Snowflake%20stored%20procedure%20execution%20is%20going%20to%20be%20available%20using%20this%20connector%20in%20the%20future%3F%20Looks%20like%20this%20would%20only%20cover%20ingesting%20data%20into%20Snowflake%20but%20not%20execute%20any%20DML%20or%20DDL%20statements%20including%20stored%20procedures.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1452815%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1452815%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F689678%22%20target%3D%22_blank%22%3E%40adfguy%3C%2FA%3E%26nbsp%3Bcurrently%20ADF%20Snowflake%20connector%20doesn't%20support%20executing%20stored%20proc.%20We%20will%20track%20the%20ask.%20Do%20you%20mind%20sharing%20your%20scenario%20with%20lookup%20%2B%20sp%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1452837%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1452837%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F694185%22%20target%3D%22_blank%22%3E%40Srini2020%3C%2FA%3E%26nbsp%3B%3CSPAN%3ESnowflake%20stored%20procedure%20execution%20is%20on%20the%20radar%20though%20we%20don't%20have%20timeline%20at%20the%20moment.%20To%20understand%20more%2C%20what%20kind%20of%20Snowflake%20DML%2FDDL%20operations%20you%20want%20to%20execute%20in%20the%20workflow%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1452891%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1452891%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F414697%22%20target%3D%22_blank%22%3E%40Linda_Wang%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BHi%20Linda.%20Hope%20you're%20doing%20good.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20created%20a%20schemaless%20dataset%20against%20the%20Snowflake%20linked%20service-%20then%20i%20used%20that%20dataset%20in%20a%20lookup%20activity%20and%20called%20a%20stored%20procedure%20from%20it.%3C%2FP%3E%3CP%3ESurprisingly-%20Stored%20proc%20ran%20just%20fine%20in%20the%20database%20but%20ADF%20doesn't%20seem%20to%20capture%20the%20return%20value%20and%20it%20fails.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20see%20the%20attached%20screenshots%20for%20more%20understanding.%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22snowflake_query_history_showing%20_success.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F197802i2C08FCFD76CD648E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22snowflake_query_history_showing%20_success.PNG%22%20alt%3D%22Query%20log%20at%20Snowflake%20level%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EQuery%20log%20at%20Snowflake%20level%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22adf_execution_log.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F197800i58E24C606BA4DC96%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22adf_execution_log.PNG%22%20alt%3D%22ADF%20execution%20log%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EADF%20execution%20log%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Lookup_activity_calling_snowflake_SP.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F197803i7D2D7F25545A6D82%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Lookup_activity_calling_snowflake_SP.PNG%22%20alt%3D%22Lookup%20activity%20configured%20to%20call%20stored%20procedure%20of%20snowflake%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3ELookup%20activity%20configured%20to%20call%20stored%20procedure%20of%20snowflake%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22schemaless_dataset.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F197801i8BAB0265D8504382%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22schemaless_dataset.PNG%22%20alt%3D%22Schemaless%20dataset%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3ESchemaless%20dataset%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1453549%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1453549%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F689678%22%20target%3D%22_blank%22%3E%40adfguy%3C%2FA%3E%26nbsp%3Bthanks%20for%20sharing%20the%20details.%20Executing%20stored%20proc%20on%20source%2Flookup%20is%20not%20supported%20now.%20The%20way%20ADF%20submits%20query%20to%20Snowflake%20doesn't%20handle%20SP%20as%20you%20observed.%26nbsp%3B%3CSPAN%3EI%20was%20trying%20to%20understand%20more%20on%20your%20workflow%20logic%20w%2F%20lookup%20%2B%20SP%20to%20see%20what%20scenario%20is%20blocked%20by%20lacking%20of%20such%20capability%2C%20or%20if%20you%20can%20use%20query%20instead.%20Hope%20it%20clarifies.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1453572%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1453572%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F414697%22%20target%3D%22_blank%22%3E%40Linda_Wang%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eso%20we%20need%20to%20wait%20till%20Stored%20Procedure%20Activity%20rolls%20out%20the%20support%20for%20Snowflake%20it%20seems.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1454103%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1454103%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F414697%22%20target%3D%22_blank%22%3E%40Linda_Wang%3C%2FA%3E%26nbsp%3B%20We%20would%20like%20to%20execute%20create%20table%20and%20insert%20into%2C%20merge%20commands%20using%20the%20Snowflake%20stored%20procedure%20activity.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1455119%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1455119%22%20slang%3D%22en-US%22%3E%3CP%3EDoes%20it%20work%20with%20Snowflake%20residing%20in%20GCP%20or%20AWS%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1455506%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1455506%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F695797%22%20target%3D%22_blank%22%3E%40Alaurier%3C%2FA%3E%26nbsp%3Bsource%20supports%20any%20Snowflake%20flavor%2C%20and%20sink%20supports%20Snowflake%20on%20Azure.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1456499%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1456499%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20ADLS%20Gen1%20support%20to%20copy%20data%20into%20snowflake%20using%20ADF.%3C%2FP%3E%3CP%3EIn%20snowflake%20we%20are%20currently%20using%20Blob%20storage%20as%20staging%20area%2C%20can%20we%20overcome%20this%20with%20ADF%20Snowflake%20connector%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1456517%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1456517%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F696480%22%20target%3D%22_blank%22%3E%40Srinivas_b14%3C%2FA%3E%26nbsp%3BUsing%20blob%20storage%20is%20still%20required%20as%20a%20staging%20for%20the%20ADF%20Snowflake%20connector%20as%20well.%20Also%20it%20only%20takes%20a%20SAS%20token%20and%20not%20a%20Managed%20Identity%20which%20makes%20it%20require%20a%20manual%20intervention%20of%20updating%20the%20SAS%20token%20when%20its%20rotated%20periodically%20for%20security%20and%20complaince.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F414697%22%20target%3D%22_blank%22%3E%40Linda_Wang%3C%2FA%3E%26nbsp%3BPlease%20correct%20me%20if%20I'm%20wrong.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1473509%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1473509%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20trying%20to%20connect%20to%20a%20snowflake%20instance%20but%20are%20receiving%20errors%20while%20setting%20up%20the%20connection%20in%20ADF.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20using%20the%20Azure%20hosted%20Integration%20Runtime%20we%20receive%20the%20following%20exception%20when%20testing%20the%20connection%3A%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CPRE%3ECURLerror%20(curl_easy_perform()%20failed)%20-%20code%3D51%20msg%3D'SSL%20peer%20certificate%20or%20SSH%20remote%20key%20was%20not%20OK'%20osCode%3D13%20osMsg%3D'Permission%20denied'%3C%2FPRE%3E%3CP%3E%3CSPAN%3EIf%20using%20a%20self%20hosted%20Integration%20Runtime%20we%20get%3A%3C%2FSPAN%3E%3C%2FP%3E%3CPRE%3ECURLerror%20(curl_easy_perform()%20failed)%20-%20code%3D60%20msg%3D'Peer%20certificate%20cannot%20be%20authenticated%20with%20given%20CA%20certificates'%20osCode%3D2%3C%2FPRE%3E%3CP%3E%3CSPAN%3EThere%20are%20no%20SSL%20certificate%20errors%20when%20trying%20to%20access%20the%20database%20through%20the%20browser.%20The%20host%20is%20on%20xxxxxxx.eu-central-1.snowflakecomputing.com.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHave%20you%20come%20upon%20this%20error%20before%3F%20Any%20pointers%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1480519%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1480519%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F414697%22%20target%3D%22_blank%22%3E%40Linda_Wang%3C%2FA%3E%26nbsp%3Ba%20stored%20proc%20activity%20(or%20something%20like%20an%20Execute%20SQL%20Task%20in%20SSIS)%20would%20be%20useful%20to%20execute%20queries%2C%20but%20also%20for%20running%20DDL%20commands%20such%20as%20CREATE%2FALTER%20WAREHOUSE.%20This%20would%20allow%20to%20scale%20a%20warehouse%20up%20at%20the%20start%20of%20the%20pipeline%20and%20scale%20it%20back%20down%20at%20the%20end.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1480564%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1480564%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F447152%22%20target%3D%22_blank%22%3E%40KoenVerbeeck%3C%2FA%3E%26nbsp%3Bthanks%20for%20the%20feedback.%20Script%20task%20for%20Snowflake%20is%20on%20our%20future%20plan%20though%20I%20don't%20have%20ETA%20to%20share%20at%20the%20moment.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1480626%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1480626%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F703204%22%20target%3D%22_blank%22%3E%40BenMcIntyre%3C%2FA%3E%26nbsp%3Bfor%20Self-hosted%20IR%2C%20please%20make%20sure%20you%20try%20with%20the%20latest%20version.%20And%20looks%20to%20me%20the%20issue%20is%20related%20to%20your%20%3CSPAN%3Enetwork%2Ffirewall%20settings%26nbsp%3B%3C%2FSPAN%3Ewhere%20some%20traffic%20is%20%3CSPAN%3Eintercepted%20or%20blocked%20(%3CA%20href%3D%22https%3A%2F%2Fcommunity.snowflake.com%2Fs%2Farticle%2FError-Peer-certificate-cannot-be-authenticated-with-given-CA-certificates%23%3A~%3Atext%3DCause%2CTLS%252FSSL%2520error%2520is%2520generated.%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcommunity.snowflake.com%2Fs%2Farticle%2FError-Peer-certificate-cannot-be-authenticated-with-given-CA-certificates%23%3A~%3Atext%3DCause%2CTLS%252FSSL%2520error%2520is%2520generated.%3C%2FA%3E)%3C%2FSPAN%3E.%20If%20the%20issue%20persist%2C%20I'd%20suggest%20you%20contact%20Snowflake%20to%20guide%20you%20troubleshoot%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1480744%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1480744%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20suggestions%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F414697%22%20target%3D%22_blank%22%3E%40Linda_Wang%3C%2FA%3E%26nbsp%3BDo%20you%20have%20any%20idea%20why%20this%20would%20happen%20when%20we%20were%20initially%20using%20the%20Azure%20hosted%20IR%3F%20We%20only%20tried%20the%20self%20hosted%20option%20as%20a%20last%20resort.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1487067%22%20slang%3D%22en-US%22%3ERe%3A%20ADF%20now%20supports%20data%20integration%20with%20Snowflake%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1487067%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F414697%22%20target%3D%22_blank%22%3E%40Linda_Wang%3C%2FA%3Ethe%20Microsoft%20documentation%20doesn't%20seem%20to%20mention%20how%20to%20create%20the%20Azure%20External%20stage%20if%20you%20enable%20staging%20with%20Snowflake%20as%20a%20sink.%20When%20the%20COPY%20INTO%20command%20gets%20generated%20and%20then%20executed%20in%20Snowflake%20it%20references%20an%20External%20stage%20that%20does%20not%20exist.%20Is%20there%20a%20plan%20to%20allow%20this%20setting%20to%20be%20controllable%20from%20within%20ADF%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Azure Data Factory provides 90+ built-in connectors allowing you to easily integrate with various data stores regardless of variety of volume, whether they are on premises or in the cloud.

 

We are glad to share that ADF newly added support for Snowflake connector with the following capabilities to fulfill your Snowflake data integration need:

  • Ingest data from Snowflake into any supported sinks (e.g. data lake) using Copy activity, which utilizes Snowflake’s COPY into <location> command to achieve the best performance;
  • Look up data from Snowflake for ADF control flow consumption using Lookup activity;
  • Load data into Snowflake from 90 plus supported sources using Copy activity, which takes advantage of Snowflake’s COPY into <table> command to achieve the best performance.

You can now find Snowflake connector from ADF connector gallery UI. Learn more from Snowflake connector documentation.

SnowflakeConnector.png

 

Upcoming:

Next, we plan to enable the following to further enrich the ADF-Snowflake integration capabilities. Stay tuned!

  • Load semi-structured data from JSON files into Snowflake VARIANT column using Copy activity, for data processing in Snowflake subsequently. [Update 2020/7/12: now data factory supports direct copy between JSON files and Snowflake semi-structured data types, learn more from direct copy from Snowflake and direct copy to Snowflake.]
  • Support Snowflake in Mapping Data Flow as source and sink transformations to provide seamless ETL. Before it’s available, you can use Copy activity in conjunction of Data Flow, e.g. perform transformation using Data Flow on top of data lake, and use Copy activity to load data into/from Snowflake.
44 Comments
Senior Member

In one of our energy client(can't take the name for confidentiality) we found the performance of ADF when loading data into Snowflake was not great. Then raised a ticket to Microsoft and MS support team advised to use Matillion inside Azure. After that we found performance of data load been increased. It's around 3/4 months old story. Does this still true for large volume of data load?

Microsoft

@avixorld this Snowflake connector utilizes Snowflake's most recommended and performant way to load data and can scale for large volume of data. Not sure what exact mechanism your client used earlier. If any perf issue going forward, please keep raising support ticket and we'd love to look into the specific case.

Regular Visitor

Great update @Linda_Wang !!!

 

I tried executing Snowflake stored procedure from Lookup activity and it succeeds at the database level but errors out in the UI - 

 

{ "errorCode": "2100", "message": "Failure happened on 'Source' side. ErrorCode=UserErrorOdbcInvalidQueryString,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=The following ODBC Query is not valid: 'call CDM.test1('c')'.,Source=Microsoft.DataTransfer.Runtime.GenericOdbcConnectors,'", "failureType": "UserError", "target": "Lookup1", "details": [] }

 

 

a known issue ?

Regular Visitor

Thank you for the update @Linda_Wang 

 

Please let us know if Snowflake stored procedure execution is going to be available using this connector in the future? Looks like this would only cover ingesting data into Snowflake but not execute any DML or DDL statements including stored procedures.

Microsoft

@adfguy currently ADF Snowflake connector doesn't support executing stored proc. We will track the ask. Do you mind sharing your scenario with lookup + sp?

Microsoft

@Srini2020 Snowflake stored procedure execution is on the radar though we don't have timeline at the moment. To understand more, what kind of Snowflake DML/DDL operations you want to execute in the workflow?

Regular Visitor

@Linda_Wang   Hi Linda. Hope you're doing good.

 

I created a schemaless dataset against the Snowflake linked service- then i used that dataset in a lookup activity and called a stored procedure from it.

Surprisingly- Stored proc ran just fine in the database but ADF doesn't seem to capture the return value and it fails.

 

Please see the attached screenshots for more understanding.Query log at Snowflake levelQuery log at Snowflake levelADF execution logADF execution logLookup activity configured to call stored procedure of snowflakeLookup activity configured to call stored procedure of snowflakeSchemaless datasetSchemaless dataset

 

 
 

 

 

 
 

 

 

Microsoft

@adfguy thanks for sharing the details. Executing stored proc on source/lookup is not supported now. The way ADF submits query to Snowflake doesn't handle SP as you observed. I was trying to understand more on your workflow logic w/ lookup + SP to see what scenario is blocked by lacking of such capability, or if you can use query instead. Hope it clarifies.

Regular Visitor

@Linda_Wang 

so we need to wait till Stored Procedure Activity rolls out the support for Snowflake it seems. 

 

Regular Visitor

@Linda_Wang  We would like to execute create table and insert into, merge commands using the Snowflake stored procedure activity.

 

Thanks

Occasional Visitor

Does it work with Snowflake residing in GCP or AWS?

Microsoft

@Alaurier source supports any Snowflake flavor, and sink supports Snowflake on Azure.

Occasional Visitor

Hi,

 

Does ADLS Gen1 support to copy data into snowflake using ADF.

In snowflake we are currently using Blob storage as staging area, can we overcome this with ADF Snowflake connector 

Regular Visitor

@Srinivas_b14 Using blob storage is still required as a staging for the ADF Snowflake connector as well. Also it only takes a SAS token and not a Managed Identity which makes it require a manual intervention of updating the SAS token when its rotated periodically for security and complaince.

@Linda_Wang Please correct me if I'm wrong.

Occasional Visitor

We are trying to connect to a snowflake instance but are receiving errors while setting up the connection in ADF.

 

If using the Azure hosted Integration Runtime we receive the following exception when testing the connection: 

CURLerror (curl_easy_perform() failed) - code=51 msg='SSL peer certificate or SSH remote key was not OK' osCode=13 osMsg='Permission denied'

If using a self hosted Integration Runtime we get:

CURLerror (curl_easy_perform() failed) - code=60 msg='Peer certificate cannot be authenticated with given CA certificates' osCode=2

There are no SSL certificate errors when trying to access the database through the browser. The host is on xxxxxxx.eu-central-1.snowflakecomputing.com.

 

Have you come upon this error before? Any pointers?

Senior Member

@Linda_Wang a stored proc activity (or something like an Execute SQL Task in SSIS) would be useful to execute queries, but also for running DDL commands such as CREATE/ALTER WAREHOUSE. This would allow to scale a warehouse up at the start of the pipeline and scale it back down at the end.

Microsoft

@KoenVerbeeck thanks for the feedback. Script task for Snowflake is on our future plan though I don't have ETA to share at the moment. 

Microsoft

@BenMcIntyre for Self-hosted IR, please make sure you try with the latest version. And looks to me the issue is related to your network/firewall settings where some traffic is intercepted or blocked (https://community.snowflake.com/s/article/Error-Peer-certificate-cannot-be-authenticated-with-given-...). If the issue persist, I'd suggest you contact Snowflake to guide you troubleshoot it.

Occasional Visitor

Thanks for the suggestions @Linda_Wang Do you have any idea why this would happen when we were initially using the Azure hosted IR? We only tried the self hosted option as a last resort.

Visitor

@Linda_Wangthe Microsoft documentation doesn't seem to mention any controls with using the Snowflake stage. It creates an external stage dynamically by default.  Is there a plan to allow this setting to be controllable from within ADF and provide the ability to reference existing Snowflake external stages?

Occasional Visitor

Hi @Linda_Wang,

 

I'm trying to use this connector, but when i try to get a sample of the data I receive this error:

JhonatanReco_0-1593496203745.png

 

However, the connection are sucessful:

JhonatanReco_1-1593496284201.png

 

I've researched this but I did not found information related :(

 

any idea? 

 

Thanks

Senior Member

Hi @JhonatanReco,

you can specify a database in the linked service:

KoenVerbeeck_0-1593504441191.png

If you have multiple databases and you don't want to create a linked service for each, you can specify a "USE myDB;" in the pre-copy script or you can just use three-part names, e.g. myDb.mySchema.myTable.

Senior Member

Sorry, with three-part name I should have specified this:

myDB.mySchema.myTable.

 

EDIT: updated in original comment.

Frequent Visitor

Adding support for Stored Procedure calls would be huge to winning over ADF adoption in Snowflake projects.  Staging data is a great start, but it leaves a gap on how to handle the data once it's in Snowflake without a 3rd party tool, or using Databricks Notebooks, or lastly using Snowflake Tasks which would break the dependency between the ADF pipeline and downstream activity.

Frequent Visitor

I have the connector working using Snowflake as the sink using the native COPY TO connector. Everything is working just fine, however I would like to add a second default column to the sink table. The COPY TO column has transformation parameters that allow for this (https://docs.snowflake.com/en/sql-reference/sql/copy-into-table.html#transformation-parameters). Is it possible to configure the column name in the ADF connector to utilize this functionality?

Occasional Visitor

@Linda_Wang Thanks for the update. This is really nice feature. We have BLOB files in JSON format and want to load into Snowflake stage. As you mentioned above , JSON format support will be there in upcoming releases.  Do you have any timeline/ETA for this JSON support feature?

Microsoft

@ChrisPuuri You are right that during each copy ADF will create external stage and clean it up at last. We don't have plan to support referencing existing external stage at the moment. Do you see any issue with current model?

Microsoft

@MartinJohnMadsen Good to know the connector works for you. I don't think Snowflake COPY INTO support adding a column w/ static value which does not exist in source, the transformation parameters can do column reordering/omission and we do leverage it for column mapping behavior. Kindly clarify if I miss anything.

Microsoft

@RavindraAsabe we are going to release loading between JSON and Snowflake VARIANT by end of this week.

Frequent Visitor

Hello, @Linda_Wang.

Thanks for responding to questions on this topic. It really helps us understand all the possibilities and limitations of this connector.

I wanted to clarify if the "ROLE" connection parameter is supported. I can see that there is no such field in the linked service view, but it can be added through "Additional connection properties".

Anyway, even having a specified role in properties or directly in a connection string - I was not able to query Snowflake due to this error:

ERROR [57P03] No active warehouse selected in the current session. Select an active warehouse with the 'use warehouse' command. 

Despite that warehouse is specified for the linked service.

'use warehouse' in a query text does not work also.

Is there any way to work around this issue?

Frequent Visitor

Thank you @Linda_Wang for working with us on this. The connector is amazing and has the potential to simplify a lot of our ELT work with Snowflake.

 

My scenario is this: the source data has three columns (C1, C2, C3) stored in a Parquet file in Blob. The target table in snowflake has 4 columns (C1, C2, C3, C4) where the last column, C4, has a default value CURRENT_TIMESTAMP(). When I manually run the copy into from an external table, I can specify the column list explicitly from the source like this:

 

copy into snowflake_table (C1, C2, C3)
from 'azure://...'
credentials=(azure_sas_token='...');

If I don't specify the column names, I get the same error I see from the ADF connector: Snowflake can't copy 3 columns of data into a table with 4 columns. But specifying the column names makes this work since the fourth column has a default value. If there were a way to configure the column name list in the connector, we could utilize the default column to timestamp every row we load with the load time (which is the goal).

 

 

Frequent Visitor

@Linda_Wang I have tested this using an explicit schema in the copy activity (excluding the column with default timestamp). That behaves as expected- the default column in Snowflake populates with the timestamp. I think this will work for us, but I wanted to follow up for anyone else who might find this.

Frequent Visitor

@AzureFrank We have exactly the same need for calling stored procedures in Snowflake from ADF. This would be a huge win for us for the same reasons you detailed above.

Visitor

Thanks @Linda_Wang no we don't have any issues creating the stages and then cleaning them up after the copy activity completes. I was just curious. It doesn't seem to create much extra overhead.

 

Our biggest need as this point will be 1) the ability to call a stored procedure or send a SQL script to Snowflake to create a table/view. This is huge for us! 2) would be the ability to load JSON's which sound like it's coming soon. Curious if the first item is on the roadmap.

Visitor

@Linda_Wang who is the appropriate team to create a ticket with when we run into issues? MSFT or Snowflake? We are seeing some issues as we deploy from a Development to Test data factory and attempt to switch the connection string to use our 'EDW_DEV' to 'EDW_TEST' database.

Microsoft

@ChrisPuuri Good to know you don't have issue nor concern on the behavior regarding external stage.

 

Snowflake stored proc support is on the plan though I don't yet have definitive timeline to share. 

Loading data between JSON files and Snowflake VARIANT is under release process and shooting for live by end of this week.

 

For the issue you mentioned, you can create ticket to MSFT to take a look first.

 

Microsoft

@MartinJohnMadsen the default mapping behavior in copy activity is to map columns by name in case-sensitive manner. It should work even the source column count is less than the sink column count, as long as all source columns exist in sink with identical names. Let know if you see differently. And explicit column mapping does also work as you mentioned.

And Snowflake stored proc activity support is on the plan.

Microsoft

@oleksandrkravchuk ADF Snowflake linked service UI currently shows the most common and basic properties, and you can extend via "Additional connection properties" e.g. to add ROLE setting.

'use warehouse' is not supported in Snowflake connector source query. When copying data from Snowflake, the query only takes single select statement.

ADF uses the warehouse you specified in the linked service during runtime. The error seems indicating the warehouse name is wrong or it's inactive. Please double check.

Frequent Visitor

@oleksandrkravchuk  @Linda_Wang We got a similar error when using the Snowflake connector. The Linked Service tested ok, but when trying to use the connector in a pipeline, we got the "use warehouse" error. We solved this by specifying a default role, namespace, and warehouse for the service account user in Snowflake. It appears that the Snowflake connector uses the default snowflake role which is typically the PUBLIC role. Hope that helps.

Occasional Visitor

@Linda_Wang do you have any sense of timing on the ability for stored procedures? We also have this requirement and would like to keep our whole workflow running in ADF, but we need the ability to execute a stored proc or at least execute some SQL from ADF to do some transformation and insert into another table.

Microsoft

@dschuler36 stored proc activity support is on our H2CY20 plan now.

Occasional Visitor

@Linda_Wang awesome, thanks for the update!

Regular Visitor

@Linda_Wang Thanks for the update. We are looking forward for this as well.

Occasional Visitor

looking forward to the stored procedure support or native sql support for ETL.  Currently this limitation is forcing us to look elsewhere - question does the databricks let us run sql procedure?