Apart from @PaigeMillers input, I don't understand why you have a do loop, since you're doing OUTPUT outside of the loop? ... View more

I was thinking about CONNECT, but since you don't have EM license on the host where the data resides, I don't think your code will work in that remote session. RLS hand is NOT meant for processing large data sets (unless they reinvented that engine totally). ... View more

Given the information on their web page, ODBC seems like the option to use for you: Drivers and Interfaces | ClickHouse Docs ... View more

This might do the trick? SAS Help Center: Schedulers Commands (job schedulers resume) ... View more

In a multi node environment it's quite common to store your data in a shared file system, or in a separate database. If that's not feasible, maybe you can cross mount the drives between the servers? Check with your infrastructure/OS team for advice.   ... View more

Not only for PROC INOMAP, this generally happens when the path doesn't exist, or maybe you lack credentials. If you are using a SAS client, e.g., Enterprise Guide, be aware that the statement executes on SAS compute (workspace) server, and any drives (E:) must be configured at system startup.   For information of the infomap use the LIST statement. SAS Help Center: Syntax: PROC INFOMAPS LIST Statement Output goes to the log, which you can redirect using PROC PRINTTO.   ... View more

This list is a combination of discontinued products and 9.4 intelligence platform specific operations. Cubes (MDDB and OLAP) are discontinued, there are migration paths for these, using Viya jobs, CAS and VA. Anything that uses 9.4 metadata-server needs to adopt to Viya 4 (no metadata server exists in the sam way in Viya). FSEDIT (FSP), if it's in use, contact any user that uses it and elaborate on alternatives for them in Viya context. Same goes for DDE. it requires a SAS Display Manager session in Windows to work. DDE is also discontinued from Microsoft. PROC SQL works in Viya (Compute), but is not executed inside CAS (where PROC FEDSQL is used instead).   Alla'n'all, you need to through those programs, evaluate what they do and why, and then plan for migration. ... View more

Depends on the source table. Second example relies on a count column in the source, the first doesn't. ... View more

Please provide an example, also what you have tried so far. ... View more

This sounds like results (e.g. output from procedures using ODS HTML) rather than the log. What happens if you chose "Add"? ... View more

Can you verify that you are using SPDE (you write "SPD" only), or perhaps SPDS? Generally speaking, those engines rock when it comes to inserts, modify/update not as much. When you have that many observations in your transaction data set, sometimes a brute force MERGE or JOIN could be quicker. ... View more

This means SAS needs to query the data to be able to assign an appropriate length, since I don't think this information is available in Parquet metadata. This is a big ask, and will potentially consume a lot of resources during libname assignment. The basic problem here is that SAS Base doesn't support VARCHAR/STRING data types. CAS does however, but your use case might not be suitable for a CAS only implementation. Maybe SAS can do something using Data Catalog agents somehow, so this can be fixed in batch (could be feasible solution for a multi user environment?). ... View more

I can't see that you can do this without losing data consistency. It seems now that you put values on the same row based on the input data order. What is the meaning of each row in the new table? ... View more

You cannot copy/move SPDE data using OS tools. This is because the directory path is coded into the table metadata. See answers above for ways of copying within SAS: ... View more

Not exactly, with that syntax. One way is to define q_ultimi_ia_3 as view instead. Or if this is the only place it's being used, paste that query in the current query as an in-line view (See @Tom's example). ... View more