How many EG users do you support? I would recommend that SCCM-type solutions, as @Nigel_Pain suggests, are only worthwhile for large user numbers. Please note that for each upgrade you would need to request a new SAS Software Depot, download it, then do the SCCM packaging.   In my experience, for small user numbers (say < 50) the "Check for Updates" facility is far preferable as it requres less work. If company policy prevents users doing this themselves, then can your help desk do the upgrade for these users applying their admin rights? Also it is perfectly OK to have users with varying versions as long as they are at least all on EG 8. It really isn't necessary for all users to be upgraded each time there is a minor upgrade.   ... View more

We provide a lot of SAS datasets to Power BI by loading them into SQL Server tables using SAS/ACCESS database connectors and that works very efficiently. While we use SAS 9.4, I'm sure this approach would work equally as well in Viya.   ... View more

Here's one way of doing this - using RETAIN requires use of a variable not being read in: data Reviews; input @1 key $3. @6 Review_Date mmddyy10.; format Review_Date date9.; datalines; 380 3/31/2023 380 9/6/2023 380 3/6/2024 380 9/18/2024 380 4/4/2025 381 2/22/2024 381 6/30/2024 381 7/1/2025 ; run; data Reviews_Want; keep key Review_Date Days; set Reviews; by key; if first.key then Days = 0; else Days = Review_Date - Last_Review_Date; output; retain Last_Review_Date; Last_Review_Date = Review_Date; run;   ... View more

What you are doing on your PC suggests to me that your multiple SAS sessions are IO bound with the PROC CONTENTS processes waiting until your permanent storage IO channels free up. I suspect your primary SAS session is first in the IO queue so is not delayed as much. Try reducing your number of remote sessions - does that reduce the lag? Also I hope you are using the WAIT = NO option on your RSUBMITs otherwise they wont run in parallel. ... View more

@PhilGUK - Yes, I have worked in the UK too but for SAS out at Marlow, many years ago. Definitely a career highlight!   Regarding our use cases for SAS/CONNECT, they are typically resource intensive especially high CPU, so the session start up time becomes immaterial. Parallelising one of our jobs reduced run time from 5 or 6 hours down to 2.5 hours so more than halved. This is purely SAS 9.4, Viya not being an option for us as yet. ... View more

It is entirely up to you what your definition of churn is and how many months of inactivity you want to base your churn indicator on. I don't have your data so I can't really provide any guidance on this. What you are suggesting makes sense. ... View more

I suspect the question is: how many months of inactivity results in permanent inactivity for the majority of customers? You want the training data to accurately reflect churn reality, that is permanent inactivity. You will need to do some analytics on your data to find out what is the inactivity period spread for most churners. ... View more

@RGarrido - Completely understand that using a CONOPTS mechanism isn't going to work with AUTHDOMAIN. Needs to be via a SAS-supported option. ... View more

@RGarrido  - The way we hide our Snowflake account and password details using SAS/ACCESS Interface to Snowflake is by creating an Authentication Domain via SAS Management Console. We then create a Snowflake user group via User Manager then add the Snowflake account and password in the Accounts tab like so: Then in the Snowflake Server connection definition in SMC, the Snowflake Authentication domain is used: You can then create Data Library definitions in SMC that use the Snowflake server and connection definitions.  ... View more

Google gives me this answer which I suggest you try (I don't have Viya to try): caslib mydbreflib desc='My Relational Database CASLIB' dataSource=(srctype='<database_type>', /* e.g., 'oracle', 'postgres', 'teradata' */ server='<database_server_address>', username='<database_username>', password='<database_password>', database='<database_name>'); proc casutil; save casdata="<cas_table_name>" /* Name of the CAS table to save */ outcaslib=mydbreflib /* CASLIB connected to your relational database */ casout="<target_table_name>" /* Name for the table in the relational database */ replace; /* Optional: Overwrites the target table if it exists */ quit; ... View more

In-memory tables are used extensively in Viya and are managed by CAS servers. As soon as a CAS server is shut down, the tables disappear. To read the tables back into memory the CAS server needs to be started and the tables read back in from permanent storage.   However Viya also has Compute servers which function just like the SAS 9.4 ones where data is read from and written to permanent storage. ... View more

True, but it isn't clear which issue the OP has: an embedded quote or simply a long end-quoted string - the option can deal with those. ... View more

Here is a doc link on how to set up Git for use with EG.  ... View more