Please provide the query (and log) so we can help analyze it, ideally with using the options in the link from @Tom. ... View more

Just to fix the output issue, you could use the of _all_ construct with catx: data _null_; set &Lib..&Mem; length out $1000; out = cats(catx(';', of _all_),';'); file "&outfile" mod lrecl=32767 encoding="utf-8"; put out; run; ... View more

It's pretty much in the message, you need to specify on which server your SAS PC Files Server is executing. This information should be documented for your environment. ... View more

I don't have the "Bulk Load" tab in my advanced settings, probably because we are using SAS/ACCESS to SQL Server, not ODBC. I'm on 9.4M8 Linux. Not sure what you refer to when you say "advanced option in ODBC set up". Do you mean ODBC Manager (Ican't fins an advanced option here)? I think it should be enough to set it on the libname, the important thing is to generate the BULKLOAD=YES when your LIBNAME statement is being generated. ... View more

There are lot of coding challenges on internet. You can use those even if they aren't SAS specific, just use SAS to solve them. One example I've couple of years is "Advent of Code". ... View more

As @MarkusWeick suggest, use a numerical date formatted column for this. data news; val = '06May1998'd; new_val = intnx('YEAR',val, 1, 'SAME'); format val new_val date9.; run; ... View more

Could this be caused by VARIANT data types? Check for lengths in all columns, do any of them exceed 32K? Also, try implicit pass-through (your query should work with the same performance, explicit pass through shouldn't be necessary here). ... View more

Another (and not ideal) work-around if you wish to use the existing transformation: - specify %let etls_debug = 1; in your job(s), or perhaps in appserver_autoexec_usermods. - Have program (macro preferably) in your postcode of your SCD2 transform (or as a separate transformation) that picks up work.etls_close, modify the end date (for records equal today - drop the rest), and re-apply it to you target table. Of course, if you are expecting a big amount of records to be closed out each batch, this is probably not acceptable from a performance standpoint. ... View more

This is a outside my realm. I found this (old) paper: https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://support.sas.com/resources/papers/proceedings/proceedings/forum2007/015-2007.pdf&ved=2ahUKEwi63Ma-vamTAxVDExAIHUkvPEkQFnoECB8QAQ&usg=AOvVaw02Ha3_unK5TGPkuKH_Td9S May contact you SAS representative or open a SAS track to get better/more detailed guidelines. One caveat, if you build you own java transformation, that will for not be eligible for migration to Viya 4 when that day comes (please verify with SAS). ... View more

That is one flaw many have discovered. Unfortunately, you cannot tweak the DI Studio native transformations, unless you a re a skilled Java developer. What you can do is take the generated code  from the standard transformation, and paste into a User Written Transformation. It will not be as "nice" as the original one, and some adjustments/configuration to make it work. ... View more

The transformation is available her:     ... View more

We have a slightly different setup, SAS Compute (corresponds to your DI Server I assume) is on the same host as LASR root (controller) node. How is your LASR defined in metadata, when it comes to Logical Server, hosts etc? Also, it doesn't look like you are using the SAS LASR Analytic Server Loader transformation?  Please share your Job diagram and the complete job code. ... View more

As an addition to @Ksharp tips, also run PROC Product_Status. It will give details on what is actually installed. ... View more

Generally speaking, SPDE does not usually speed up writing, because the data is still fed in single thread. But it has a flip side when it comes to updating indexes, which is done in parallel while inserting data. And of course, querying the data... ... View more