I found this: SAS for Life Sciences | SAS There is whole are arround CDISC: SAS and the Clinical Data Interchange Standards Consortium (CDISC) | SAS There are dedicated groups like: http://www.phuse.eu/css and much on: Lex Jansen's Homepage SAS Solutions are mostly build on the metdataserver (Enterprise Intelligence Platform) BI/Di server and their tools. For analysts Eguide is mostly the offered approach, you can do coding in that like old classic DMS SAS. http://www.sas.com/offices/europe/sweden/pdf/Forum03_swecom.pdf  name pheedit is used with sas 8.2 and sas 9.1 http://www.sascommunity.org/seugi/SFI2004/E530.pdf (2004) ... View more

Your are having a web-service with SAS with A StoredProcess Server? That is having (seen many times 3) sub process as simulteanous processing-load balancing. You have that, and it is SAS. Your are using "PROC SQL" having multiple logical processors in the machine it will do multi-threading. (Parallel processing) there options to switch it off on. You have that and it is SAS. So my prorosal is rather simpel. - switch multithreading off - define two Stored Process servers.    One with those 3 subworkers for light queries   One with one worker for the heavy load queries - Look for the OS options to prioritize at the OS level. - try to offload heavy queries into batch (sas batch-jobs) processing and let then run planned/scheduled. By  that light query users being serviced  getting the best possible. All other workoad being spread. Using Windows Unix (Linux) or Mianframe as server running SAS? They are all Multi-users Multi-process/tasking operating systems. Trying to operate those is handeling the logic  simulteanously/parallel processing. The babbage machine is history. ... View more

Sumit, you are have the classical performance&tuning problem no doubt about that. You mentioned them your options (the classic ones) : a/ buy better hardware (your hardware is limited) b/ Let the queries better perform  (optimize code) c/ Spread of load, prioritze classes of them This was common about 1980's with very expensive hardware (mainframes) to cheap labor human hours as I started as SystemsProgrammer. Workloadmanager (WLM) is the approach to tell online (interactive users) getting more priority than batch usage. Scheduling usage for planning and running as fast a possible the needed batch-jobs. http://en.wikipedia.org/wiki/Thrashing_(computer_science) was the one to fear for limited resources on cpu/memory. You are describing the same behavior (toss). Getting the machine overloaded it get ionto a process of not proceeding anything. To cancel long running queries als the Ivory-tower IT-man will not help you. Load will go up as users are trying to put more into it (restarting). An option for spread/balance load on machine is mentioned. make several classes. Fast queries (limited in usage) / heavy big queries. And limit the option on parallel / simultanous processing. Allowing less (decrease) work to the machine will increase the performance and troughput. (counter intuitive!)               ... View more

Get back to changes that did happen when it got broke. Can you eliminate the possible cause is macAfee? (Would not be the first and last time) Your deal with IT is a bad one. As they can change everything and you are needing your part and theirs to solve it.  ... View more

If your SAS installation is UTF compliant (DBCS) and your encoding is UTF in SAS what is this question about? http://support.sas.com/documentation/cdl/en/nlsref/64811/HTML/default/viewer.htm#n0882t2muy4l94n19cno6z40xmuz.htmhttp://support.sas.com/documentation/cdl/en/nlsref/64811/HTML/default/viewer.htm#n0882t2muy4l94n19cno6z40xmuz.htm ... View more

Congratelations, You are beyond your comfortzone, having a big volume (big queries) variety.  I a missing the velocity. That is "Big data" :smileygrin: Just kidding on that. But it looks to be you have a performance&tuning problem.  The best way would be to prevent it happen. SAS(R) 9.4 SQL Procedure User's Guide ( Using PROC SQL Options to Create and Debug Queries)   Another is you did not mention whether a external DBMS is involved or not. Sometimes a classic OLTP RDBMS admin can limit the resources on that side of the query. In that case you have to dig into the implicit/explicit sql pass through. When it are SAS-datasets also a lot is possible like definining indexes for often used quiries. Proc SQL is multithreading it could use more cpu-time than the wall clock time. With this I never have seen something at Proc SQL limits on resources. You have a WEB-interface so you are in the situation to limit the code of the users not being able to do the bad things. It is like preventing the SQL-injection abuse. If the users are needing free format code and free format queries you have an issue. I remember once something having seen in SMC but I cannot figure it out anymore. SAS(R) 9.2 Intelligence Platform: System Administration Guide, Second Edition (Welcome | Communities on SASUsing SAS Management Console to Monitor SAS Servers)    Monitoring performance tuning: http://support.sas.com/resources/papers/proceedings13/463-2013.pdf    http://www2.sas.com/proceedings/forum2008/387-2008.pdfIt is the most disappreciated kind of work. You are bothering business users as the computer does not do what they want. You are bothering IT-staff as those beautifull machines are being stressed and destroyed by the business users. You are bothering managers as nobody is happy.    ... View more

Sumit,  There are a lot of timers everywhere. Your stored process can run by a Web-based connection or by Eguide. You have to more specific about your question and the problem you are trying to solve. Think off: - Browser time-out. (Internet Explorer)   but also Eguide has time-outs - Web-server time outs - Firewall/routers time-outs - Session time-outs. For this see: SAS(R) 9.4 Stored Processes: Developer's Guide (STPSRVSET Function  inhertited from SAS/intrnet) If there is a load-balancing problem there are multiple processes for one Stored ProcessServer. Interactive processes should respond quick enough. (less than a minute, more in the seconds) Longer running processes should be scheduled. With scheduling mostly there is an expected end time with an options alert signalling when something is going not as should be. Always the contradiction having it run for some additional time it would finish to the decision to stop the proces.  Stopping a proces could also possible having impact on the consistency of the data. By the way Stored Processes are Service processes started by the first requestor  and will be reused by possible many requestors afterwards. When something wrong is done by one requestor it is possible to have this service process got blocked. The only solution is to kill a blocked service process on the OS-level. StoredProcesses should be well tested before giving into procution when having a good serviced operation. Splitting multiple users groups to have their own appsrv context is another. ... View more

When you are using Eguide is will be a client/server approach. The Server can be your local desktop but a lot of power will come from servers and the most proposed ones are Unix based (Linux redhat suse and Aix). You can recognize that if you need to define a profile to reach a server.  Workspace Servers are just  one type of objects that can be defined.  SAS libraries and data elements can also be defined and redefined. That redefining can be done witht Information map studio. That manual is showing some of what is done.  SAS(R) Information Map Studio 4.2: Getting Started with SAS(R) Information Maps (Creating Data Items) is showing dates being defned as types. They are still numeric as it is normal SAS on the backgound there. Going into details you can add descriptions to elements. In DI is something found for it. SAS(R) Data Integration Studio 4.7: User's Guide (Add a Note or Document to a Registered Object) It are the tools for modeling describing the data. There are interfaces to other tools doing this in the same way . With these descritpions new code can be generated. Not coding by hand but defining relationships with transformations. By that the metdatabase will become something containing information in a similar way as you would do change-management to source-code. The fun of this approach is that when it is complete you can easily have and use tools for analysing impacts in those relations and logic.     SAS(R) Data Integration Studio 4.7: User's Guide (impact analysis) ... View more