Hi again, Patrick! After chatting with Qualtrics (the survey tool folks), and confirming that the survey is open to everyone, we're wondering if the IPs being used on the VPN are restricted at SAS. We can't be sure of that, though. The Qualtrics folks have the following recommendations, if you are so inclined to try again to access the survey: Disable the VPN Temporarily: VPNs can sometimes route your traffic through servers that are blocked or not recognized by the survey’s security settings, causing access issues. Try disabling Bitdefender VPN and accessing the survey link again. Check Your Location Settings: Even if you select a United States server, some VPN IP addresses may be flagged or restricted by the survey’s security or by Qualtrics’ own geo-blocking measures. Accessing the survey from your actual country of residence (without VPN) is recommended. Clear Browser Cache and Cookies: Sometimes, cached data can interfere with access. Clear your browser’s cache and cookies, then try the link again. Update Your Browser: Make sure your browser is up to date, as outdated browsers can sometimes cause compatibility issues. Thanks again for making me aware of the issue! ... View more

For simplicity, SAS treats the Microsoft Fabric Data Warehouse as a SQL Server endpoint. Microsoft provides this endpoint—known as the SQL analytics endpoint or TDS endpoint—as part of Fabric to enable compatibility with third-party applications. SAS leverages this endpoint using existing SQL Server drivers (e.g., ODBC Driver 18 or later), allowing SAS to connect and query data in Fabric without requiring custom connectors. This approach aligns with Microsoft’s design, which exposes the Fabric Data Warehouse through a Tabular Data Stream (TDS) protocol, the same protocol used by SQL Server. This means SAS can interact with Fabric in much the same way it does with traditional SQL Server databases, simplifying integration and reducing the need for specialized configuration. However, it’s important to note that Fabric’s SQL analytics endpoint is currently read-only, and writing data into OneLake may require alternative methods such as REST API calls or using supported file formats like Parquet. How to Connect - Microsoft Fabric | Microsoft Learn SAS Help Center: Access an Azure SQL Database ... View more

Actually, this is not a SAS 9.4 to SAS Viya migration. We are migrating a SAS 9.4 on-prem DI environment to Azure where future ETL processes will be developed using Azure-based tools. Since I have only read access (no data access), I wanted to ask:   Is there any automation or tool-based approach to extract job dependencies and logic from SAS DI? Or any recommended way to directly move or replicate SAS DI jobs into Azure using migration utilities or frameworks? Any insights or experiences on large-scale SAS DI to Azure migration would be really helpful. ... View more

It feels like "something happened" and SAS overreacted. Backward compatibility was imho always an important selling point for SAS. I believe that it would have been more than sufficient for these functions to be disabled as a default but with some option to enable them - something similar to noxcmd. ... View more

I did engage both SAS and Databricks tech support, but I am exploring alternatives in parallel. ... View more

hello thanks to your advices I managed to optimise very much. I have a column "send date" in the big table so I added a criteria inside the inner join expression to limite the rows that are > of begining of the month. many thanks. Nasser ... View more

BTW, if there is a prior error in your program, your DATA step creating the macro variables won't execute, so your macro variables wont be created. You might want to check that possibility. ... View more

Your RegEx needs some amendment. Below should work. data test; infile datalines4 truncover; input line $256.; if prxmatch('/^\%let etls_\w+.+;$/i', strip(line)) then delete; datalines4; %let etls_startTime = %sysfunc(datetime(),datetime.); %let etls_recordsBefore = 0; %let etls_recordsAfter = 0; ;;;; But as @MrSantos already advised, you should use the SAS  Content Assessment Tool with it's migration tools.  What you're doing would only make sense if you wouldn't want to migrate to SAS Studio flows but to simple .sas programs ...but this would only make sense imho if the SAS Viya version you've licensed doesn't allow for the direct migration to SAS Studio Flow.  ... View more

"How can I know what is the libaname  code that connect between sas and tera here??? I dont need to run the libaname in order to run it but I think that in background it is running but I dont know what  libname is running ." Do you want to know specifically what Terdata instructions the libname statement triggers? Try this before your libname: options sastrace="d,,,ds" sastraceloc=saslog nostsuffix msglevel=i; If you are interested what SQL is sent down, you can settle for: options sastrace=",,,d" sastraceloc=saslog nostsuffix msglevel=i;   ... View more

Since you are only pulling over some of the columns it should not be that hard to use elimination to determine which one SAS considers as using a data type it does not support.   But I wonder what you mean by creating time of a VIEW?  And why you want to know it? The last time a view is modified would be the last time the view's definition was changed.  Is that what you need to know?  If you want to know the last time the DATA that the view might surface was changed you probably will need to check the modification times of the TABLES that the view queries. ... View more

Assuming you're running whole flows with multiple programs, the traditional approach would be to determine the critical path, identify the longest running program on this critical path and in there the longest running steps. You can often get quick wins just by tweaking these long running steps.  Run your programs with option fullstimer which provides additional info that's important for choosing a good performance tuning approach. ... View more

We can't know what your SAS scripts like HYFI_INTExpSF.sas are actually doing but if the create text files then it's highly likely that they use a SAS table as source to create these text files.  As others already mentioned Proc Compare works on SAS tables and not text files. If your current scripts create these text files as a 1:1 export from SAS tables AND if these SAS tables are permanent, then you could of course write another SAS script that uses Proc Compare and compares the source SAS tables.    ... View more

@Kurt_Bremser wrote: The ALU (Arithmetic-Logical Unit) in a processor can only do operations with two numbers/values at a time, and as long as there's no other precedence, the calculation is done left to right. Thanks for contributing this great argument, which is also consistent with the "left to right" order of evaluation in "Group 3" of the table "Order of Operation in Compound Expressions." ... View more

yes i already do that with firstname and lastname but i think i'll change the sensibility level thanks ... View more

@whymath wrote: Thank you. I am shocked, does that means the supervisor will return control to the top of data step, after running DOW-Loop? What's the usage of this feature? That is how the data step works.   It does not care (or even really know) that you put the SET statement inside a DO loop.   Most data steps are like your first one, they stop when they read past their inputs. 2 data _null_; 3 put _n_= eof= 'BEFORE'; 4 set oneobs end=eof; 5 put _n_= eof= 'AFTER'; 6 run; _N_=1 eof=0 BEFORE _N_=1 eof=1 AFTER _N_=2 eof=1 BEFORE NOTE: There were 1 observations read from the data set WORK.ONEOBS. NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 second But you can explicitly tell it when to stop, like in your second one. 8 data _null_; 9 put _n_= eof= 'BEFORE'; 10 set oneobs end=eof; 11 put _n_= eof= 'AFTER'; 12 stop; 13 run; _N_=1 eof=0 BEFORE _N_=1 eof=1 AFTER NOTE: There were 1 observations read from the data set WORK.ONEOBS. NOTE: DATA statement used (Total process time): real time 0.01 seconds cpu time 0.00 seconds Or if there are no inputs at all then it knows not to start are second iteration. 15 data _null_; 16 put _n_= bmi= 'BEFORE'; 17 bmi=(180*0.4536)/(75*0.0254)**2; 18 put _n_= bmi= 'AFTER'; 19 run; _N_=1 bmi=. BEFORE _N_=1 bmi=22.498604997 AFTER NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds And if there are inputs but you complete an iteration without actually advancing any of the inputs then it stops and says it is because of looping. 21 data _null_; 22 put _n_= eof= 'BEFORE'; 23 if _N_=1 then set oneobs end=eof; 24 put _n_= eof= 'AFTER'; 25 run; _N_=1 eof=0 BEFORE _N_=1 eof=1 AFTER _N_=2 eof=1 BEFORE _N_=2 eof=1 AFTER NOTE: DATA STEP stopped due to looping. NOTE: There were 1 observations read from the data set WORK.ONEOBS. NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds ... View more