SAS Users
Providing technical tips and support information, written for and by SAS users.
In this post we dig deeper into the fourth recommended practice for securing the SAS-Hadoop environment through Kerberos authentication: When configuring SAS and Hadoop jointly in a high-performance environment, ensure that all SAS servers are recognized by Kerberos. Before explaining the complex steps in connecting to secure Hadoop within a
➤ DISCLOSURE! In June 2018 Google introduced changes to the way it handles its Maps platform. They now require API key in order to embed a map, plus Google Maps "projects" must now be associated with a billing account. Unless these new Google rules are met, Google maps described in
The only thing that’s constant is change. The continual cycle of computing changes leads to common questions about the effects of these changes—operating systems are getting upgraded, customers are moving to new SAS clients, upgrading to new releases of SAS, working with new Java and browser versions. All of these
In previous posts, we’ve shared the importance of understanding the fundamentals of Kerberos authentication and how we can simplify processes by placing SAS and Hadoop in the same realm. For SAS applications to interact with a secure Hadoop environment, we must address the third key practice: Ensure Kerberos prerequisites are met
When SAS is used for analysis on large volumes of data (in the gigabytes), SAS reads and writes the data using large block sequential IO. To gain the optimal performance from the hardware when doing these IOs, we strongly suggest that you review the information below to ensure that the
Report design includes several phases. Granted, these phases aren’t official: they’re more a reflection of my own thought processes and how my report designs typically unfold: the initial “get the data on the screen to see what we have” phase the addition of filters and prompts to assist with guided