You can use PROC TRANSPOSE as in this example:  https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.4/proc/n01rzqgzs8vq1bn10h1wtx914kyf.htm   If you want actual code, you will need to provide data in a usable form, as seen in these examples and instructions.   PS: I understand that a key person wants the data in this form; but please understand that is the only reason to do this. If you are programming for yourself, and want to use the results in further analyses, tables or plots, you would never do this transpose. As stated by @Kurt_Bremser , this transposed arrangement of the data makes all other programming much more difficult. ... View more

@FreelanceReinh wrote:   Yes, it looks like those mathematical inaccuracies occurred too frequently in Copilot's training data. Sadly, it's not just using words wrong. It doesn't do calculations properly either. One day I was lazy and asked Copilot to compute MPH for my walk, in which I walked 3 miles (exactly) in 56 minutes and 36 seconds. Copilot walked me through the math and for the first step, Copilot told me that 56 minutes and 36 seconds is 56.61 minutes. Can you spot the error? (it's a small error but certainly not round-off error) There was another math error in the next calculation as well. ... View more

I asked an AI chatbot (Copilot) why traffic is way down at internet help sites. The answer:   Traffic on StackOverflow and similar help sites is down because several structural shifts all hit at once, and the data is now overwhelming: generative AI replaced most routine Q&A, moderation friction pushed newcomers away, and expert contributors withdrew when their effort stopped being rewarded. The collapse is not subtle — question volume is down 29× from its peak, and many sites are back to launch‑year activity levels.   Interesting how Copilot does not seem to recognize that multiplication and division are not the same thing. Down 29x is not the same as 1/29th. I do realize that many people make this same mistake in their speech and in their writing. ... View more

It would still help if you would be specific, instead of using the very vague word "processing". I'm sure many people here have good ideas on how to handle large data sets, but we can't help you unless we know what you going to do next.   Also, how big is this data set, in terms of rows and columns? ... View more

I would like to suggest that splitting data sets like this is rarely needed and is rarely a good idea, and it usually makes the next steps in your programming more difficult. If you tell what you plan to do next with this data, we could advise on a better approach.   If, for example, you want to perform a regression analysis on each split, you can do so like this (and of course this method applies to almost every PROC even if it is not regression)   data large_set1; set large_set; id=mod(_n_,10); run; proc sort data=large_set1; by id; run; proc freq data=large_set1; by id; model y=x; run;   ... View more

Partial Least Squares ought to be mentioned here. In my opinion, it is the best modeling tool when you have collinearity among the X variables, and is widely used in some areas, like spectroscopy (and of course is used in many other areas). Please see the paper by Tobias (of SAS Institute), in which he takes 1,000 highly correlated predictors, and still obtains a useful model, without all the time-consuming messiness of reducing variables. Also see the paper by Bartell (from JMP) here. ... View more

Perhaps the %NRSTR function will work here. But yes, definitely show us your code. In fact, please, from now on, ALWAYS show us your code in the first post on a topic.  ... View more

Agreeing with @Tom that numbers should not characters.   Once you perform the conversion to have numeric values, PROC SUMMARY or PROC MEANS produces the dataset or output you want. ... View more

SAS has never (as far as I know) used the normal distribution when there are more than 30 data points. It uses the t-distribution even when there are 30,000 data points (or more) assuming of course that the t-distribution is the correct distribution for the problem.   The idea of using the normal distribution when there are more than 30 data points is an approximation, and was useful back in the days before computers and you had to use a look-up table. But it isn't really needed with modern computers. ... View more

Are you using PROC VARMAX? It would appear that the parameter estimates follow a t-distribution. According to the documentation, the parameter estimates converge to a multivariate normal distribution as T approaches infinity (T apparently is the number of data points), which means before they converge they are likely a t-distribution. ... View more

As I said in another one your suggestions, I don't think this belongs in Suggestions. When some numbers aren't displayed as you want, you could simply apply the right format/function to the data before displaying it. SAS already gives you all the tools to display dates, datetimes and times in whatever way you want.   So if you have a variable named DATETIME which contains year, date, month, hours, minutes, seconds and milliseconds, you could create a new variable which contains the time part and format it as you wish.   In a SAS data step   hour_min = timepart(datetime); format hour_min hhmm.; ... View more

I'm not sure this belongs in the Suggestions section. It seems easy for you to change. (And by the way, you don't say how your data set is created, but it may be that whoever created the data set included the commas for some reason. There is really nothing in SAS that forces these numbers to have commas.)   If these are numeric, you can simply change the format to remove the commas. If these are character, you can use the COMPRESS function to get rid of the commas. ... View more

@Tecla1 wrote: Good Morning.... Tnks fo your replay... I receive this error: ERROR: Insufficient authorization to access /Totale_campioni_polizze_addebiti__&des..XLSX.   This is why you ALWAYS need to include the log when you have code the doesn't work. There's no way we could have guessed from your code and extremely brief description that this is the problem. And we want not just the error message, but the code in the log that precedes the error message, you need to show us at least one PROC or DATA step in the log before the error message.   I think @Quentin has the right answer. ... View more

Posting code that doesn't work, without a log, is usually not productive. ALWAYS show us the log. And we need to see not just the error messages; we need to see the preceding code as well, covering one whole PROC or DATA step before the error message.   Also, the description of the problem is way too brief: "I'm not able in any way to put more sheet in the same file."  ... View more

SAS offers many tutorial videos about SAS Viya. There's even one called "SAS Viya Quick Start".   https://video.sas.com/category/videos/sas-viya-quick-start   ... View more