One thing I do when I'm in a situation like this, if the scenario fits:   i) delete overall dataset ii) in a macro, read in the data to a temp dataset, append to the overall dataset, delete the temp dataset   And then cycle the macro for all of the datasets. That way the single datasets that are input won't show up in the project. Tom ... View more

1. Is it actually a SAS dataset, or is it a dataset in some other format that you were using in SAS? 2. Do you now have the file physically on your PC? 3. Do you know anything about the data contained in the file?   Tom ... View more

I was sure it would be fine, and I was right... data abc; length 'E-mail_Address'n $5; 'E-mail_Address'n = "def"; output; 'E-mail_Address'n = "ghi"; output; run; 24 25 data abc; 26 length 'E-mail_Address'n $5; 27 'E-mail_Address'n = "def"; output; 28 'E-mail_Address'n = "ghi"; output; 29 run; NOTE: The data set WORK.ABC has 2 observations and 1 variables. NOTE: DATA statement used (Total process time): real time 0.02 seconds cpu time 0.00 seconds ... View more

Yes, I've noticed MANY unhelpful CLI messages over the years. I think once you reach that point in the stack, you're out of the SAS ecosystem; makes you appreciate good SAS diagnostics all the more!   Tom ... View more

Go to support.sas.com, down a bit there's a button for "Technical Support". Click it. You've done 1 and 2, so click 3 "Contact Technical Support", and you'll be guided into a dialogue to get in touch with them. I suggest you follow the "Create a Track" stream, it's what I always do and it works well.   I've had excellent support from them for over 20 years. Good luck!    Tom ... View more

Well, as it says, SAS ran out of memory!   There are a number of possibilities.   SAS has three memory size options, MAXMEMQUERY, MEMSIZE, and REALMEMSIZE. One of them may need to be adjusted. Unfortunately, that's a job that is generally done by someone with SAS experience. If you can find that person at your shop, ask them to give you a hand with changing these.   Also, do a search on your error message. I just did that, and a number of the hits discussed the nature of the model (I'm not experienced enough with OPTMODEL to have an opinion). Perhaps your request needs to be tweaked.   SAS has a wonderful Technical Support group. I typically wouldn't send someone with your problem to them, as I don't think it's a software issue, but because of your inexperience I think it might be necessary. Put in a track with them, and see what they say.   Make sure you post back with the solution so everyone else can learn from it!    Tom ... View more

Interesting problem.   Is it possible to do the following?   1. Display a few of the values that are of concern in SAS showing the full 15 significant digits.   2. Have these variables uploaded to Snowflake in the usual way.   3. Download them to SAS again, and again display the full 15 significant digits.   It would be good to see how much the variables are changing, as opposed to truncating/rounding for display.   Tom ... View more

Yes, but...   I couldn't find a way to do it using the EG point-and-click features. It's very easy to do in a code window. First, you have to turn off all of the result options in Tools -> Options -> the Results tab. Then submit code looking something like this:   ods _all_ close; ods excel file="C:\Some Directory\SASTest.xlsx" style=EGDefault options(embedded_titles="no" embedded_footnotes="no" sheet_interval="proc"); proc print data=sashelp.class; run; proc means data=sashelp.cars; class make; var cylinders; run; proc tabulate data=sashelp.shoes; class region; var sales; table region, sales*sum; run; ods _all_ close;   In your case, if you're comfortable, you can just grab the code generated in your 4 proc reports, and drop them into a program together. Hopefully, someone a bit better with ODS will have a better suggestion. Tom ... View more

If you're generating a lot of "report" output (to a destination like PDF, HTML ...) it can take a very long time for EG to get this output back from the server. Double check that you're not creating a huge report that you don't realize.   Tom ... View more

One problem is that there are several layers in the stack that are doing things concurrently:   - The DBMS is retrieving the data from its own disk. - The data is being passed over a network to a SAS server. (Note that EG is actually only a client, which generates and submits SAS code to a SAS process somewhere, which may or may not be on the same machine that EG is running on). - The SAS server is doing whatever it is supposed to do with the data. - Results are being passed over a network to your EG session on your machine.   When I need to troubleshoot issues like this, I try to verify that each layer is performing properly: 1. I use a tool like TOAD to submit the SQL query, and see how long the database takes to process it. 2. Same, but on the server that SAS is running on to see if network issues are a problem. 3. Submit the SAS code directly from a SAS session on the SAS server. Again, do problems appear? 4. Are there any communication bottlenecks between the SAS server and your PC? From the comments you're making, it sounds like either your SAS process is on your local PC, or the SAS process is generating a huge amount of output and downloading it to EG, which isn't common.   As you're a new user, I know that some of these steps may be challenging. If you have access to SAS expertise at your organization, it would be a good idea to bring them into the discussion.   There is a SASTRACE system option that can give you some visibility into what is being submitted to your DBMS. ... View more