As Ted notes, in our case, the only data the server sees is on the server. Fortunately, we are allowed to see the portion of file structure on the server that holds our data.

Warren Schlechte Learn how you can help Texas State Parks

-----Original Message----- From: Kirby, Ted [mailto:ted.kirby@LEWIN.COM] Sent: Tuesday, March 06, 2012 1:17 PM Subject: Re: Switching from Local PC version of SAS to Server Based version Pros and Cons

For the past 15 years of which I am aware, we have always had access to SAS on a network server (with its own drive letter) in addition to the local computer installation of SAS. The network server has its own SAS installation (that is slightly different from the local PC installation). Every job that I have run on the server (i.e., through Remote submit) always runs faster than the local installation of SAS. Thus, when dealing with large datasets I always run SAS on the Server.

For us, there is no having data on your local machine but running SAS on the server. The SAS server cannot "see" anything but itself. Thus, all data must be on the SAS server. The one disadvantage to this setup is that we cannot "see" (i.e., through SAS Explorer or Windows Explorer) anything in the "work" directory. The reason for this is that the temporary work space used by SAS is buried on the server and is unavailable to anyone except IT staff.

-----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Ben Powell Sent: Tuesday, March 06, 2012 4:03 AM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: Switching from Local PC version of SAS to Server Based version Pros and Cons

As the previous reply suggested local bandwidth would only be an issue here if you were using large local datasets which does not appear to be the case. As such I would rule local bandwidth out as a potential cause of your slow server performance.

Even if you do have a bandwidth constraint that would not impact on the the server being able to do its job. So, you would need to get a handle on the typical server bottlenecks which might be memory, CPU, I/O, or fileserver/database connection performance, if the data is not all on the SAS server.

If using a Win box, taskmgr; linux I like htop; tea-leaves if you're using MF. If you're using a Mac best pay a visit to your local genius bar and have a latte,

Regards ************* IMPORTANT - PLEASE READ ********************

This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.