I suggest that the answers to this will depend a lot on your use case. If your requirement is ad-hoc analytics, then what you do in SAS versus Python might be based on your skill level in each. For analytics you want to productionise, then using SAS for the majority of workflow processes and embedding PROC PYTHON steps is an obvious option.  ... View more

%RETURN terminates the current macro, not your SAS session. You need to post your code so we can figure out what is happening. ... View more

@doesper  - You can use a LIBNAME statement with SQL passthru like this: libname SF snow <Snowflake connection definition>; proc sql; connect using SF; select * from connection to S (SELECT * FROM MySnowFlakeTable); disconnect from SF; quit; Also I suggest you checkout Redshift options for trimming VARCHAR columns. There is one for Snowflake for example which you can call using the CONOPTS option: libname SF snow <Snowflake connection definition> conopts = 'default_varchar_size=256'; ... View more

There's already a SCANSTRINGCOLUMNS option implemented for some external databases. I can't see it as an option in SAS/ACCESS Interface to Redshift in SAS 9.4 though. It is available in SAS/ACCESS Interface to ODBC though if you have that. What SAS database connectors do you require it for?  ... View more

Are you referring to SAS Viya for Learners or a different Viya installation? ... View more

If I'm dealing with large logs, I run such jobs in batch mode, then log size doesn't matter hence no log clearing is necessary. That also frees up your user interface of choice to just concentrate on development work. ... View more

I ran your test program on M8 and got identical results to you.   I'd suggest opening a Tech Support track as they are more likely to know about maintenance level differences and any fixes. ... View more

IMHO PROC COMPARE is such a useful tool and is one of my most frequently used ones. It's invaluable for developers to check the impact of process changes, but also for administrators to confirm if data is identical across SAS environments.   It could definitely do with a bit of love though, as its reporting capabilities still seem to be stuck in pre-ODS days.   ... View more

Can you post a test program that reproduces the problem plus a screenshot of the PDF produced? We can run it in a later maintenance release to see if it behaves the same. ... View more

The usual place to start when investigating problems of this type is server logs. Since you have already worked with your platform administrator I'm guessing that's already happened. Opening a track with Tech Support is the next best option since more troubleshooting will be needed. ... View more

Very cunning! ... View more

If EG is running local SAS on your PC then there is already the CALL SOUND routine which you can try. You can even play a tune if you so wish 😊   Of course this isn't an option if EG uses remote SAS servers. ... View more

I'm wondering if there's some unprintable characters in the load data upsetting the layout of bulk load file. Maybe try bulk loading a small sample first. ... View more

What happens if you don't use the BULKLOAD option? Still the same errors? Also what version and maintenance level of SAS is this? ... View more

This worked fine for me. I created a test PPTX in Powerpoint, saved it to a SAS server folder, ran the below program. I just double-clicked on the email attachment and the Powerpoint opened as I expected: filename mymail email "[email protected]" subject="PPTX Test" attach=("TestPPTX.pptx" content_type="application/pptx" ); data _null_; file mymail; put 'Hi Me,'; put 'This is a test.'; run; This is the test email:   ... View more