Encoding is just an entry (one line) in the configuration file used when calling SAS. You can see what configuration file(s) are used on your server session by running proc options.   ... View more

Thanks! The business user is going to insert it into his script and make the comparison.   In the meantime there's a bigger problem.   We know that the SAS-script executed in the daily batch uses LATIN-9 (ISO-8859-15) encoding. We also know that the SQL Server target database uses "Danish_Norwegian_CI_AS" encoding/collation. Yet all occurrences of ÆØÅ from the various sources appear as '?' in SQL Server.   Is there a kind of conflict/inconsistency between how LATIN9 and "Danish_Norwegian_CI_AS" treats ÆØÅ? If so, I'd appreciate any suggestions on how to resolve it. I assume we'll need some kind of encoding logic in the SAS-script. ... View more

@PaigeMiller thank you. Yes, the implicitly subscripted array and the 'do over' syntax are not documented anymore.    Call me old-fashioned, but I still like to use the implicit array from time to time 🙂 Mainly because of the simplicity of the syntax. ... View more

You should use latin1 encoding. See here.  ... View more

@andreas_lds wrote: Interesting: you can set compress in the libname-statement, but the information is not in sashelp.vlibnam, but in sashelp.vtable (or dictionary.tables). There are a lot of LIBNAME settings that cannot be determined from that metadata.   Note that the default setting for compress that is defined for the libref can be overridden at the dataset level via the dataset option COMPRESS=. Also SAS will sometimes override the users setting completely.  If you try to add compression to a very skinny dataset then SAS will turn it off since it will just make the dataset larger.   So even if you could find the libref level default setitng it wouldn't really tell you anything other than what default compression MIGHT be applied to the next dataset created using that libref. ... View more

@EinarRoed TO_DATE() will work for explicit pass-through. If you're using SAS SQL (implicit pass-through) then use for missing dates an expression like '01JAN1900'd and make sure that the variable you assign this value to has a format of date9. assigned - any date. format actually; just something which tells the SAS/Access engine that the SAS numeric variable contains a SAS Datetime value so it gets converted correctly to a Netezza DATE value.   If you have datetime values on the SAS side then use '01JAN1900 00:00:00'dt and a format of datetime21. ... View more

Another thing to look at would be your database commit settings. If your job is committing for every row for example that would slow your processing drastically. Try increasing this setting to see if it improves performance. ... View more

Hi Astounding; I used your code in my program and it worked (i.e. when I run my data for this year, I get January and February YTD Data.  When I use your code, I get just January data).  So, it works great!  As I`m learning, I would like to understand the last part of the code.  I guess as I read it the (intnx("month", today(),-1)<=calendar_dt) makes sense to me (but doesn`t work on it`s own).  I`d like to better understand why it works when the last part (<intnx("month",today(),0)) is added to the code.  Thank you   (intnx("month", today(),-1)<=calendar_dt<intnx("month",today(),0)) ... View more

This shows an example: %let input_key=CUSTOMER_ID, BANK_ID; %put %scan(%quote(&input_key.),1,%str(,)); %put %scan(%quote(&input_key.),2,%str(,)); ... View more