"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
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 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
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
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;
In SP4, you can export OLAP cubes into .xml files. Right click the Cube from SAS OLAP Cube Studio, select 'Export Cube'. This is an appropriate part of a migration strategy through dev-test-production, since they can then be imported through the 'Import Cube' button on the left menubar.
Three different setups for SAS JMP are listed below. Upwards compatibility (i.e. level 1 to 2) available, downwards less likely (like we know STPs are not). Level 1. SAS JMP and SAS Base installed and licensed on individual desktop/laptop. Level 2. SAS Integration Technologies installed on server, SAS JMP installed
