Another option that I'm using frequently for autocall macros: options mautolocdisplay; With this option a log message get printed that tells you where the macro has been compiled from whenever you use the macro. ... View more

If attach to the output dataset means storing it in a variable of this dataset then below is a straightforward way of achieving this. data want; set sashelp.class end=last; length my_logic $400; if last then do; my_logic=cats('%let wtcalc1=',"&wtcalc1;",'%let wtcalc2=',"&wtcalc2;",'%let wtcalc3=',"&wtcalc3;"); end; run; ... View more

"We are migrating a SAS 9.4 on-prem DI environment to Azure where future ETL processes will be developed using Azure-based tools" So are you initially migrating from a on-prem SAS 9.4 to an Azure cloud based SAS 9.4 or is this from start about replacing SAS 9.4 with something else like Databricks?   A SAS 9.4 on-prem to SAS 9.4 Azure migration is certainly very doable and there are SAS provided tools & scripts that can support such a migration.   A replacement of SAS 9.4 is a totally different story and will require much more planning. If you search a bit then you'll find 3rd party providers who offer automation tools. I don't know though how much their claims match reality. With the rapid growth of AI there might be tools in the not so far future which will make such migration much easier. Right now it's from what I know still a labour intensive and costly exercise that will require very good planning and the right people for it not to fail.   job dependencies You should be able to derive this from the scheduler used. Or you could also use the information which output table from one job get used as input tables by another job. With DIS AND if the tables got actually registered in SAS metadata that's something you could work out scripted via SAS Metadata queries.   and logic from SAS DI Well: DIS is used to define jobs but it's the DIS generated SAS code that actually gets executed. And it's not uncommon that not all DIS steps are fully metadata driven but are just using manually created SAS code in first place. You would need to analyse both the SAS DIS metadata and the generated SAS code to fully derive the logic - and that requires good SAS skills to do efficiently. ... View more

What do you mean by SAS to Azure? To which SAS version are you migrating to? If this is about a SAS9.4 to SAS Viya migration then use SAS Content Assessment. ... View more

@CherylCoyle  It's not an issue for me but I felt you/SAS might want to know about this limitation. ... View more

I'm using Bitdefender VPN. If on a secured connection, your link returns below. This also happens if I'm connecting via the United States and not my country of residence.     Without Bitdefender VPN:   With Bitdefender VPN United States:     ... 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

@fnajera If you don't get an answer here, contact SAS Tech Support. They can give you an official answer where things are at. ... View more

@Nasser_DRMCP wrote: hello thanks for your respons. I tested what tom has suggested. and the 2 codes take the same time, arroud 10 min   nasser And that's o.k. for you or not? Make sure you look into the readbuff value. If it's set to the default of 1 then increasing this value will highly likely improve elapsed time further. And depending on your data and disk I/O adding compress=yes could also help. ... 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

In case the data step you shared is within a macro, the macro variables created could be in local scope.  If that's the issue then try with below amendments.     ... View more

... should I make a join between the two big vertica tables ? or should I , first, create a sas table filtered on model and the sent month. and join this sas table on the second vertica table ? With both tables in Vertica you certainly should push the join to the database to reduce the data volume before it gets transferred to SAS. I'd be going for an inner join like @Tom already proposed and test with a single model. Once that performs sufficiently, a single query with all the models at once will highly likely return the best overall performance.   You can write this SQL explicit (using Vertica SQL flavour) or implicit (using SAS SQL flavour). If using implicit SQL you need to ensure to only use syntax that SAS can get fully convert to Vertica SQL as else SAS will need to first pull the data to the SAS side (which certainly will have a significant impact on performance).    And for Vertica: If you know how the data is distributed over the nodes, then it could also make a significant performance difference how you formulate your join condition. The less data Vertica needs to move between nodes, the better it will perform.    Also make sure that you set libname option readbuff to something like 10000 (or even bigger depending on memory available). The default is 1 meaning Vertica will send only 1 row at a time to SAS.   If you share your current SQL syntax with us then we can eventually provide further guidance. ... View more

Based on some Copilot Q&A please try below and let us know if this works for you. Select TableName, CreatorName, CAST(CreateTimeStamp AS VARCHAR(26)) AS CreateTimeStamp, LastAlterName, CAST(LastAlterTimeStamp AS VARCHAR(26)) AS LastAlterTimeStamp, AccessCount, CAST(LastAccessTimeStamp AS VARCHAR(26)) AS LastAccessTimeStamp from DBC.Tables Where upper(DataBaseName) = 'DWP_VALL' And TAblename = 'VBM374_USED_BRANCH_CUSTOMER' ... View more

It appears that libname teradata is pre-assigned. If you've got SMC or SAS DIS then you could look into the library metadata definition. You can also run libname teradata list; to get more information.   I personally prefer using a libname over your first way because it can be used directly within any Proc or data step. But of course sometimes it's advantageous to use explicit teradata SQL that allows you to better reduce data volumes on the Teradata side. The following is a variant to your first way but uses the libname definition. libname mytera teradata .....; proc sql; connect using mytera; create table WAY1 as select * from connection to mytera ( select top 5 * from VBM374_USED_BRANCH_CUSTOMER ); disconnect from mytera; quit ; In your sample case where the libref is teradata it would of course be connect using teradata; and you also wouldn't need the libname statement because the library is already assigned. ... View more