Thanks again for your answers.   You all mentioned the number of SAS users and sharing work between users as main benefits of SAS Server. But what about having models in production. aren't automating, scheduling and sequencing calculations as important as the other points? (excuse my English)   Thanks ... View more

you forgot the set statement with the table containing your variable start_time. ... View more

This is the log, the result of the execution of your code, and not the code. Can you the code you executed that you find in the editor ? ... View more

Can you please share your code ? ... View more

Hi,   1) Here's an example that you can execute   data _null_; month=put(datepart("01OCT2015:15:22:22"dt),worddatx9.); put month=; run; - 01OCT2015:15:22:22 is a datetime. To convert it to a date you can use datepart function. - worddatw9. is a format that displays the date's month. - put function creates a string based on the format applyed.     2)  proc sql; create table want as select month ,count(1) as nb_cars ,count(distinct cars) as nb_distinct_cars from have group by month ; quit;   Hope this helps !   ... View more

Hi @WendyCzika,   Thanks for your answer.   So this is a test for the significance of the coefficients. H0 would be beta=0 and H1 beta<> 0.    In fact, all the documentation that I found mentioned the chi-square test  that we find in the output result but none of them has mentioned the T-value (In the regression hp node result there is a graphic of it), nor the Tscore.   Thanks         ... View more

Sorry but it didn't work, I found that I don't have the licence for IML...(I've never worked with IML) ... View more

I ran the program and It took 50 seconds to create the table and 6 seconds to calculate the max.   As I mentioned in a previous comment, I have 200 million lines and not 10 millions. I tried on a subset of 50M and it took 2 minutes 30 seconds.   I then tried the compress option when creating a compressed version of the 50 M table. It took 1:20 which is a good improvement.   So the solution is mainly related with the size of the data. I store the SAS data from an oracle database. so every numeric data has a length of 8.    I will think of taking less variables from the original table, and define a smaller length for numeric variables (3 for flags for example). then I will add a compress=yes (or binary or char, I must reread some papers about this). and then sort and create necessary indexes.     I think this will save disk space and execution time.   Thank you for your help and effort! Really useful advices 🙂   MK ... View more

This is very clear thanks.   In fact I didn't compress it yet. I use this table to do joins. That's why I sorted it and created an index on it. I don't know if the index still work if I compress it. In addition, I'm not sure if the dataset should be uncompressed each time I work on it, so it takes more time...   I will compress it and tell you the result !   Thanks    MK   ... View more

@Rick_SAS,   1) 86 variables 2) 24 character variables 3) only one variable.   Yes, I totally understand this, and I think that's why it's kind of frustrating, Because if there was less variables, it would be very fast ! If there's a solution I think it can be more than a solution for this particular situation, but also probably a best practice when working with large data.    MK   ... View more

hi @user24feb,   thanks for your program and your effort.   here the fastest way is proc sql. hash table is slower due to loading data into memory.   Doing the calculation with a dataset with only one variable is really fast. I think as I mentioned in an other comment, the problem appears when working with a large dataset with many variables (especially character variable).   MK ... View more

Hi @Kurt_Bremser,   Thanks for your answer.   I think you're right about calculating the max of a variable over the WHOLE dataset. And here the difference is in the number of columns and their size (many character variables with length >20 caracters for example).   I created a table with only the variable on which I want to calculate the max.   data variable_only; set have (keep=variable); run; creating the table with the dataset option keep=variable took approximately the same time of the max calculation. Although I have a SSD disk, the operation was very slow (let's say ~5mb per second)   After this, I computed the max using sql : proc sql; select max(variable) from variable_only; quit; and it took only few seconds.   So It's working with data containing all variables that makes it slow, even when working with keep= or equivalent... ... View more

Hi @Rick_SAS,   here is the output of the log (it's a french version):     SYSVLONG = 9.04.01M3P062415 26 proc options option=memsize value; 27 run; SAS (r) Proprietary Software Version 9.4 TS1M3 Informations sur la valeur de l'option SAS MEMSIZE Valeur :14014924800 Etendue : SAS Session Comment la valeur d'option est définie : Config File Nom du fichier de config. : C:\Program Files\SASHome\SASFoundation\9.4\nls\fr\sasv9.cfg ... View more