Thanks. Minor typo on page 9 of the PDF file. Macro variable names often contain special characters, ... I assume you meant say variable VALUES instead of variable NAMES.  Macro variable names could never contain any special characters because they follow normal SAS naming conventions.   And this question in the Q&A is simple if you just take a minute to think about it. Why do you not need & before list in the final example that uses %superq? Answer: I don’t really know why …. Good question.   I’ve just accepted this as a code developer’s whim. If you added an & then that would mean you want to pass the VALUE of the macro variable to %SUPERQ().  But SUPERQ wants the NAME of the macro variable.  If you tried to pass the value and it contains one of the special characters then you would need to pre-quote the value before %SUPERQ() could see.  And if you did want to quote the value you could just use %BQUOTE().   Where you might use & when calling %SUPERQ() is when you want to generate the NAME at execution time.    So perhaps you have a macro variable with the name of another macro variable.  This code will add macro quoting to the value of the NAME1 macro variable. %let myvar=name1; %let &myvar = %superq(&myvar); Or perhaps you have series a macro variables with the same basename and different suffixes. data _null_; set sashelp.class; call symputx(cats('name',_n_),name); run; %let basename=name; %let suffix=1; %let &basename.&suffix = %superq(&basename.&suffix);   ... View more

Point the libref at the DIRECTORY that contains the FILE that is the SAS dataset. libname pg1 "S:/workshop/EPG1V2/data/"; ... View more

How many observations does that query return?  You can test it in Snowflake or just wrap it into something like: .... select * from connection to sf (select count(*) as nobs from (... the query goes here ...) a ); If you want to move a LOT of data then you might get better results using Snowflakes ability to generate a CSV file into some place like Amazon S3 bucket that you could then read with SAS code to make a dataset.   Are any of those variables defined as STRING in Snowflake?  SAS datasets only have two types of variables.  Fixed length character strings and floating point numbers. So when you have a character variable of unknown length in your Snowflake table  SAS will use some default length for the variable when making the dataset.  It might pick something very long such as SAS's maximum length of 32,767 bytes.  That would make the processes of creating the SAS dataset take a very long time even if the transfer from Snowflake ran quickly.   Try just pulling over a handful of the observations (Snowflake's version of SQL should support something like a LIMIT clause to trim the number of observations returned by the query).  You can then run PROC CONTENTS on the resulting SAS dataset and see how the variables are defined. ... View more

@ivarenho wrote: Yes when i did try to run that in the past i got and still get two errors the first is library pg is not in valid format for access method random and error in lib name statement, so i would assume i need to go back and reformat the data? You will need to show the log for the actual code you ran.  Instead of taking pictures of the text just copy the text from the LOG and paste it into the pop-up window you get when you click on the Insert Code icon (looks like </>).   Most likely a message like that would be generated if you tried to point a libref at a FILE instead of a DIRECTORY.  Here is an example using a dataset I have in my home directory on the SAS server. 73 libname x "~/class.sas7bdat"; ERROR: Library X is not in a valid format for access method RANDOM. ERROR: Error in the LIBNAME statement. 74 libname x "~"; NOTE: Libref X was successfully assigned as follows: Engine: V9 Physical Name: /home/tom.abernathy 75 data _null_; 76 set x.class; 77 put (_all_) (=); 78 run; Student Name=Alfred Sex=M Age=14 Height=69 Weight=112.5 Student Name=Alice Sex=F Age=13 Height=56.5 Weight=84 Student Name=Barbara Sex=F Age=13 Height=65.3 Weight=98 Student Name=Carol Sex=F Age=14 Height=62.8 Weight=102.5 Student Name=Henry Sex=M Age=14 Height=63.5 Weight=102.5 Student Name=James Sex=M Age=12 Height=57.3 Weight=83 Student Name=Jane Sex=F Age=12 Height=59.8 Weight=84.5 Student Name=Janet Sex=F Age=15 Height=62.5 Weight=112.5 Student Name=Jeffrey Sex=M Age=13 Height=62.5 Weight=84 Student Name=John Sex=M Age=12 Height=59 Weight=99.5 Student Name=Joyce Sex=F Age=11 Height=51.3 Weight=50.5 Student Name=Judy Sex=F Age=14 Height=64.3 Weight=90 Student Name=Louise Sex=F Age=12 Height=56.3 Weight=77 Student Name=Mary Sex=F Age=15 Height=66.5 Weight=112 Student Name=Philip Sex=M Age=16 Height=72 Weight=150 Student Name=Robert Sex=M Age=12 Height=64.8 Weight=128 Student Name=Ronald Sex=M Age=15 Height=67 Weight=133 Student Name=Thomas Sex=M Age=11 Height=57.5 Weight=85 Student Name=William Sex=M Age=15 Height=66.5 Weight=112 NOTE: There were 19 observations read from the data set X.CLASS. NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds   ... View more

@ivarenho wrote: In the autoexec. sas file i have libname pg1 "S/workshop/EPG1V2/"; but when I tried to change it to storm_final.sas7bdat I got an error I believe. So that is not a valid path.    If your SAS session is running on a Windows machine then you need a colon after the S drive letter.  S:/workshop/EPG1V2/   If your SAS session is running on a Unix machine then you need a fully qualified path. So the path needs to start with the root node.   /S/workshop/EPG1V2/   The path used in the LIBNAME statement needs to point to a directory ("folder") and not to a file, so storm_final.sas7bdat should not appear in the LIBNAME statement that defines the PG1 libref.   In the photograph you posted you can see in the SAS/Studio Files and Folders tab that there is no sas7bdat files in that EPG1V2 folder.  Perhaps you should be using the data subfolder? S:/workshop/EPG1V2/data/ Reread the instructions.   In SAS/Studio expand the data folder and check if the storm_final.sas7bdat file is there.  If you can find the file then right click on the folder that contains it and ask for Properties.  That should show you the exact string you need to use in the LIBNAME statement to point to that location.   If you cannot find the file then go back to the earlier steps that setup the files and make sure they worked.  Perhaps when you ran those steps you also had the wrong path in the LIBNAME statement and so the dataset was never created. ... View more

That is not unique to VIYA.  The SAS/Studio interface used in SAS ODA does the same thing.  I have seen similar things in other editors WORD and VSCODE.  I believe the idea is to let you know where else that text appears.  That might be useful if you planned to do a global replace   In regular SAS/Studio you can find your cursor again if you press the left or right arrow key.  That will move the cursor and remove the highlighting. ... View more

Then why did you use WKS in your graph code as the XAXIS? Shouldn't that be a variable that has the month (or the re-coded month)?   My guess is that you want to use the PANELBY feature of PROC SGPLOT to make multiply graphs on a single page where the individual graphs use different ranges of XAXIS values and different orders.   If that is NOT true then do what @Ksharp said and just run two PROC SGPLOT statements.  One with the set of values that use the JAN -- DEC axis and another that uses the NOV--OCT axis.   Or you might want to use the ability of ODS itself to organize multiple "pages" into one page.  Check out ODS LAYOUT.   If you want someone to help you work out the details then provide some example data, does not need to be the real data.         ... View more

I still do not understand what your data is. Please share some data. And explain it.  So you have variable named HARVEST that appears to mean either a MONTH number or an ORDER number (or perhaps both?).  Perhaps you should split that information into two separate variables?   You have one data step that maps HARVEST into a new variable named TAG.  But it only does that for some of the observations.  For the other observations you do not give TAG a value. Was TAG an existing variable already?  How is it related to HARVEST.   And then later you replace the HARVEST/TAG variable in the graph with a third variable named WKS.   What is the meaning of WKS?  What types of values does it have?  From your last picture it seems to have also had the HARVEST. format attached to it and so it looks like it has values of 1,3,4,5,6 and 8.  What do those values mean?   ... View more

@SASMom2 wrote: Thank you for all your help! When I tried to run a Snowflake query that pull data from one table, it ran quickly but when I tried q query that pulls data from 5 tables in Snowflake, it kept running. Finally, I stopped it after 5 hours. When I run the same query directly in Snowflake, it runs in under a minute. So, I would definitely be using your method  for queries that use one table but not for queries that use multiple tables. I was hoping that it would work for complicated queries as it would save a lot of manually going back and forth between Snowflake and SAS. Thank you! Without an example I can only guess what you did.  But here are some possibilities:   You somehow asked SAS to execute the joins instead of giving the whole query to Snowflake to run.  If you ended up doing that then SAS would probably try to pull the whole table over and then join them which could take a very long time.  For example do NOT do something like this: select * from work.mytable a left join snow.dbtable b on a.id = b.id ; Instead either upload the list SAS dataset into Snowflake then then perform the join completely in Snowflake.   The sizes of the result sets was vastly different between the two queries and so you are seeing how slow your connection to Snowflake is.     There are options you can turn on to have SAS write the SQL it sends to Snowflake into the SAS log so you can see exactly what SAS ended up asking to be run.  https://documentation.sas.com/doc/en/workbenchcdc/v_001/vwbacdata/n0sa0yux9sqf90n1ttzxhko2cit4.htm   You can then try running that code in Snowflake and time how long it takes.       ... View more

Why?  Are you trying to do code generation?   You can use SAS's macro language to do code generation. %let fname = 'ABC'; %let lname = 'DEFG'; %let BMTH= '9999-12-31'; .... proc sql ; .... where first_name=&fname and last_name=&lname and DOB = &BMTH .... ... View more

Remove the partial EXECUTE statement, that is what is missing the ().  It does not look like you are trying to execute anything so you don't need that statement.   Note that everything inside the () after the FROM CONNECTION TO xx clause has to be valid Snowflake SQL syntax. ... View more

You can use SAS code to execute queries in Snowflake.  If you already have a LIBREF defined pointing to Snowflake database then that should be all you need.   You can use PROC SQL to run queries.  First make the connection by using the CONNECT USING statement.  Then you can use  the EXECUTE statement to run a command that does not return any output. Or the FROM CONNECTION TO clause for one that does.   So let's assume you defined the libref SNOW pointing to Snowflake  proc sql; connect using snow; execute by snow (...some Snowflake command...); create table want as select * from connection to snow (... some Snowflake query ...) ; quit; You can use the front end tool Enterprise Guide to create and run the SAS code.   ... View more