SAS Users
Providing technical tips and support information, written for and by SAS users.
Based on my previous posts, we are almost done with the basics of SAS libraries and how the various clients can access them. Before we leave this topic and go onto third-party database engines, I wanted to spend a few minutes talking about some best practices for making sure that
Everyone may find bad dates in their data set from time to time, but it’s often difficult to tell if they’re mere annoyances or indicative of a larger problem. Luckily, Lucheng Shao has come to the rescue in his SAS Global Forum winning paper, Don’t Let a Bad Date Ruin
Like most SAS users and administrators, you usually don't know where your backend SAS servers are located--probably in some basement server farm or perhaps another building or even another town. But I'm sure you do know that your SAS client application must have a way to reach services running on
First of all, congratulations to everyone who presented at SAS Global Forum 2013. Your hard work and contributions are what make it a success each year. Even though SAS Global Forum 2013 has come and gone, all of the papers and presentations are still available online. Out of this fantastic
John Heaton is no stranger to the often frustrating process of migrating code between environments after software updates. While release management and version control may often be afterthoughts, Heaton cautions that ignoring them could be “time consuming and disastrous should errors occur.” His winning SAS Global Forum paper SAS® Release
Reading Jan Bigalke’s SAS Global Forum paper on “Hardening a SAS® Installation on a multi tier installation on Linux" reminded me of baking apple stack cake with my mother. Neither is a simple project. Both are time-consuming, and their success depends on how skillfully you handle each layer. Data security