Hello,
I have a pre-assigned sas library for snowflake and we need to use bulkload and bulkunload with the internal stage concept using the pre-assigned library.
All our sas code are pass through code and we dont define any libname statement. In the code , we directly use the pre-assigned library and as far as I read, we cant use bulkload or unload in pass -through.
so thought of using this paramter on sas library on SMC.
Where to define this setting on library? We have other options tab ( under Advanced options ) as well as extended attribute tab ? Can we able to add it over there? I tried few options and it failed.
I need to add BULKLOAD=YES , BULKUNLOAD=YES, BL_INTERNAL_STAGE='@~' , BL_DELETE_DATAFILE=YES,BL_COMPRESS=YES
FYI. we do have a single SAS library for snowflake and it will be used for both load and unload.
Any help is much appreciated. Thanks
There's no reason why you can't use LIBNAMEs with Passthru to Snowflake. We use them. They look like this:
libname SF snow <Snowflake connection definition>;
proc sql;
connect using SF;
select * from connection to SF
(SELECT * FROM MySnowFlakeTable);
disconnect from SF;
quit;
Also you should be able to add the bulk loading options to the LIBNAME also.
so thought of using this paramter on sas library on SMC.
Where to define this setting on library? We have other options tab ( under Advanced options ) as well as extended attribute tab ? Can we able to add it over there? I tried few options and it failed.
I need to add BULKLOAD=YES , BULKUNLOAD=YES, BL_INTERNAL_STAGE='@~' , BL_DELETE_DATAFILE=YES,BL_COMPRESS=YES
The correct place to do this in SAS Management Console is as you noted on the library properties -> Options tab -> Advanced Options button -> Other Options tab
Carl Sommer - SAS Technical Support
@freshstarter - Actually we use pre-assigned Snowflake libraries exclusively also. I just used the LIBNAME statement as an illustration 🙂.
You don't want to use the semi-colons. To test this out, temporarily mark the library as not pre-assigned, set your advanced options, and then display the generated libname statement for the library. That makes it much more straight-forward to understand how the options are being included. Once you can generate a libname statement that actually works when submitted, then mark it preassigned once again.
Carl Sommer - SAS Technical Support
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.