Well, we love our crackberries so much that now we can get our SAS graphs pushed out to the small screen. http://support.sas.com/kb/26/171.html
Tag: business intelligence
I have used this with much success with clients' Windows servers. It makes searching on .sas batch programs, determining which sas.exe is for what BI server, etc. Use the 'Find' function and simply type in the .sas file or BI service component you are looking for. This also provides more
For Web Report Studio reports to have drill through to detail, the associated Information Map must have drill-through to detail option selected.
In order to have the BI Manager Plug in available on a client machine, don't forget that Foundation Services and Query & Report Services are required in plan file.
If a SAS data view needs to be added to the SAS Metadata, utilize the Import Tables wizard in the SAS Management Console (SMC). "If you use PROC METALIB to import metadata for a SAS® view, the procedure incorrectly assigns a value of DATA to the MemberType attribute. The value
"I have been doing a lot of performance testing recently with the Teradata access engine vs the ODBC access engine on the same Teradata instance, and from the same server the ODBC access engine on Sybase IQ. Setup: This is all done from a SAS 9.1.3 SP4 installation, with the
I wanted to share a trick/technique with you all regarding making it easier to migrate EG projects from one environment to another. The issue is that there are often occasions where it is necessary to code file paths in an EG project (just like in any other SAS program) and
When trying to generate rollup measures for further statitical analysis from an OLAP cube, completing in MDX proved much more efficient then querying and running PROC MEANS steps. Included is an example of how to utilize the DRILLUPMEMBER() function in MDX code: http://www.databasejournal.com/features/mssql/article.php/10894_3572621_2
![LSF Users Guide clear.gif](https://blogs.sas.com/content/sastraining/files/2009/10/clear.gif)
I’ve never found a great user guide, not to say that one doesn’t exist. You should be able to schedule any type of executable/job like a batch file from using the Platform LSF client tools (packaged with the server tools). You can also use command line executables like bsub and
![Grabbing the Data Creation Date clear.gif](https://blogs.sas.com/content/sastraining/files/2009/10/clear.gif)
The data table creation date is sometimes necessary, say in the footnote of your stored process. Included below is a sample to retrieve this date from the file system. /*Open the dataset*/ %let dsid=%sysfunc(open(sashelp.shoes)); data _null_; /*grab the CRDTE function*/ ddate=%sysfunc(attrn(&dsid;,CRDTE )); /*Format in DDMONYY*/ call symput('ddate', put(ddate, dtdate9.)); run;