I've been spending my weekends developing a SAS Publishing book proposal. (For those interested, it involves learning how to fully leverage SAS Stored Processes as a beginning programmer.) Creating examples and jumping between coding, testing and then writing about everything, I have had a heck of a time with my
According to the SAS Documentation http://support.sas.com/resources/thirdpartysupport/v92m3/browsers.html Windows 7 machines should use Internet Explorer 8. Unfortunately Microsoft will no longer allow installations of IE 8 on Windows 7 machines. http://windows.microsoft.com/en-US/internet-explorer/downloads/ie-8 I was able to get all the web applications to work on Google Chrome however the BI Dashboard appears but not all
Just got some time to begin playing with the 9.3 Enterprise Business Intelligence installation on my SAS laptop. As I was testing out the web applications, SASWebDoc opened but I couldn't get to the SAS login screen up to access the SAS Stored Process web application. First I started perusing my
In order to support a SAS Server Architecture, administrators must know where all the log files from the various SAS Business Intelligence services are located. By default, each service that generates a log will create it within the services' own configuration folder structure. For example, the metadata server log is
In 9.2, the right-mouse click functionality is not available by default. To switch back to this (which for STP developers in a DEV environment is essential to our productivity), SAS has provided the following note: http://support.sas.com/kb/39/292.html As you can see, out-of-the-box, all SAS STP developers will need to do is
In SAS 9.2, internal accounts can be created and utilized within the metadata and then do not require host (or domain) accounts defined elsewhere. By default, the sasadm@saspw is one such internal account. Unless you specifically declare an exception, the server-level policies for routine password resetting and locking (such as
SAS Web Application Infrastructure automatically logs users out of the system after a predesignated amount of time. Unless the user has the URL bookmarked, they have to retype the Web Application URL. There is a much less frustrating way for users to get back in, allow the user login button
There is a wide array of papers (from SAS, conferences, on blog posts, etc) discussing the need to move WORK (the SAS temporary files) off to other locations. In the SAS Intelligence Platform it's the same way, however there are a BUNCH of SAS configuration files to start worrying with.
Developing an OLAP cube, testing in Enterprise Guide or Web Report Studio, and suddenly you begin getting error messages from rebuilding the OLAP Cube stating that it's locked. Now what do you do? Restart the OLAP Server? Well, if you don't have access to the server itself or others are
Included are two quick references to tuning OLAP Cubes: Server Tuning Information ~ http://support.sas.com/documentation/cdl/en/biasag/61237/HTML/default/viewer.htm#a003145996.htm Cube Tuning Information ~ http://support.sas.com/documentation/cdl/en/olapug/59574/HTML/default/viewer.htm#a002605609.htm Also, you can add aggregations to the OLAP cube to improve performance. As mentioned in my earlier post, you should consider doing Advanced Aggregation Tuning to provide presummarized measures of various
