Hello @blueskyxyz  "the new proposal involves saving all of these files on an FTP server while still running the SAS code on our existing server" is not a practical solution. An appropriate approach would be to mount the remote location on to your SAS server and save files there. As a reminder temp/work folder needs to be on a local storage AND accessing a remote network location for read/write would add to latency or slowness.   ... View more

Hello @MG18  The error message is clear. Suggest that you contact SAS Tech Support if you have a valid sid file. ... View more

The following link provide the location of the log files SAS 9.4 https://go.documentation.sas.com/doc/en/bicdc/9.4/bisag/p1ausbmrrybuynn1xnxb6jmdfarz.htm  https://documentation.sas.com/doc/en/bicdc/9.4/bimtag/n1ih0exzxu35f3n1xfec5udk1l3f.htm  In a typical organization, there are policies for log retention/archiving. If there is none, then create a policy, document it and follow it.   ... View more

Hello @skarnew  Your library is referencing a physical location d:\dwh\PA\CDS\Data and there are no tables existing. From the error message it appears that you are trying to perform some operation on the non-existent table /dataset PERIOD_BASE. The error message is apparently correct. What exactly are you trying to do? ... View more

hanks @SASJedi  for the update.  ... View more

Hello @Suki99  You can use Proc fedSQL as suggested by @SASJedi if you have SAS Viya. However, if you are using SAS 9.4 and don't have FedSQL, you can try the following. The output table will have the  first 10 ruws from the  result set. I have used the data from the post by @SASJedi  proc sql outobs=10; create table work.want as select * from exposure order by dosedate; quit; ... View more

Notes in the log can be suppressed by using the following option. This will suppress all notes subsequent from the point where it is used in the code.   option nonotes; To re enable the notes you can use the following. option notes;     ... View more

Hello @Anshul2  The SAS SQL optimizer selects the best option for join. In your case I am sure it selects the hash join algorithm. You can verify running the Proc SQL with _method_ option. Your log will show that it is using hash join I am sure it will. I see you are using "select *". Review if you actually need all columns. You can focus on other approaches to review your query. ... View more

Hell @sukalyan  There are many reasons that can cause this error. It says connection refused. Your identity may not be there in the metadata server. The appropriate approach is to contact your SAS Administrator. ... View more

Hello@hhchenfx  A clean install would not know of the E drive on its own. Did you make any changes to sasv9.cfg or have sasv9_usermod.cfg? Is your drive local to the PC or a remote shared drive? ... View more

Hello @melhaf  I agree with what @ballardw has said. You must modify your path statement as follows %let Path= C:\Desktop\My folder ; As a reminder while creating a macro variable, anything between the = and semicolon  ; are a part of the macro variable including quotes. ... View more

Hello @Mushy  If the intention of the import is to get data, then disable the macros and save it as xlsx. Then it should be possible to get the data into SAS. ... View more

Hello @texasmfp  As has been pointed out by others your SAS stored process on 9.4 can safely do them. However this  "It will require payment by a customer in exchange for a report." will require something more than that is already built into SAS. I suggest you approach SAS Tech Support ... View more

Hello @techsassy  When asking about the single large partition I was asking about the drive on the laptop/Desktop and not the shared drive. My preference on laptop / desktop is that OS and that comes on it is the C drive and datasets/codes should be on a different partition say for example D drive. If the data drive (D) becomes full, your OS being on a separate partition is not impacted and vice versa.  Shared drives are larger and that is how they are meant to be.  You said that "One issue that I've often noticed with SAS EG throughout the years is that, after using other working platforms (Excel spreadsheets, Chrome browser tabs, etc.), when I try to switch back to Enterprise Guide, it very regularly hangs for anywhere from 10 to 30 seconds before I can interact with it again" The browser cache is local to the system and in normal course stored on your local drive. It is very much possible that the excel files are stored locally or an a faster shared drive. That is why they work fine. I looked for the specification of Dell 3480. It is Dell precision workstation with NVME disk. That explains why Excel and  Chrome are faster. Your EG may be referencing remote shared drives. Shared drives are not local and depending upon the type and local architecture   some latency is expected.  The best thing is to work with your local IT team as they know the environment and can help better.   ... View more