I had in interesting and long conversation with one of the stalwarts in the SAS community the other day that somewhat surprised me. One of the things that I’ve always used with SAS on a Windows Server has been SAS/Connect. SAS/Connect is the piece of software that allows your SAS desktop session talk to SAS on the server. I’ve always liked it and use it when it’s available.
My friend pointed out that in his opinion, SAS/Connect is pretty old school and should only be considered on the mainframe and that there are many other alternatives that are better when connecting to and using SAS on a server. He pointed out that lots of sites use Citrix or Windows Terminal Server Services that do the job better with less hassle.
So now I’m wondering if the client server model that I’ve always subscribed to and worked with is deficient and outmoded. I’m curious how others who have multiple platforms, work in your environments. Do you use SAS/Connect and do you have any thoughts on using Terminal Services in place of SAS/Connect?
In using WPS on a server, there is not a similar product to SAS/Connect and that is why I wrote MQSubmit that allows you to batch submit WPS code to the server from your desktop ,notebook or netbook. My work is rarely interactive in building systems and tend to be heavily weighted towards running processes that reproducible in batch environments. How do other seasoned SAS developers work? Do find yourself moving between interactive and non-interactive models?