To Calculate The Size Of SAS DataSet BY Proc Contents

Hi,

 For most of the cases to optimize the system, we would be in need of the size of the data set, to set some SAS System options like : SORTSIZE, MEMSIZE, REALMEMSIZE etc.

 To Calculate size of any SAS dataset:-

 For example we want to calculate the size of a data set named as "Calculate" which one is in library named as "Base". Just create the data set that contains one observation and all the number of variables we are in need.

                                                        Data base.Calculate;

                                                        input name $18. Age 2. Salary 6. ;

                                                        Cards;

                                                        Uma Shanker Saini 30 300000

                                                         ;

                                                         run;

                                                         Proc print;

                                                         run;

 Now run the CONTENTS procedure with the data set "Calculate".

                                                      Proc contents data=Base.Calculate;

                                                      Run;





The size of the Calculate data set would depend on the data set page size and the total number of observation in  data set.

Formula to calculate :-

 Number of data pages =  1 + (floor( observations / Max observation per page))

Size = 256 + ( Data set page size * number of data pages)

 * floor is a function which is to round the value

 Now as per our example :

 Number of data pages = 1 + (floor(1/101))

 Data set size = 256 + 4096*1 = 4352

 Thus the Calculate data set uses 4,352 bytes of storage space.

How To Reduce Entries In SAS Log

Hi,

Try to use some SAS options - including macro and system (hardware related) to decrease the size of your log.

NOMPRINT       -Removes SAS statements that are generated by macro execution

ERROR=1         -Minimize the number of error to be shown in log to one by default it is 20

NOECHOAUTO  -No autoexec code in Log

MSGLEVEL     - Set to N - It will display notes, warning and errors in log

MSGLEVEL     - Set to I - It will display additional notes like index, merge, sort utility and all

NONOTES      - Suppress the notes in log

NOSOURCE /NOSOURCE2     - Suppress the primary and secondary source information in SAS log

NODTRESET     - Suppress the date and time in the SAS Log

NOWARNING     - Suppress the warning messages in the SAS Log

•  You can try more options like : NOMTRACE, NOMLOGIC, NOMACROGEN, NOSYMBOLGEN, NOCPUID, NOECHOAUTO,NOOVP, Page No=min


•  You can also try to run Proc options first the search for all the options which are containing log and try to use NO with that options (use only if exists)

Kindly use as per your convenient because of use of every options suppresses the different things in log.

 

SDLC Phases And Documents Into SDLC 2.0

Phase                                                                     Documents

1.      Project Initiation --------------------------    Project Charter

2. (a) Plan and Analysis -------------------------    Project Execution Plan

2. (b) Plan and Analysis -------------------------    Requirement Document

2. (c) Plan and Analysis -------------------------    Test Strategy

3. (a) Design ------------------------------------    Solution Architecture Document

3. (b) Design ------------------------------------    Security Interaction Document

3. (c) Design ------------------------------------    Detailed Design Document

4. (a) Build --------------------------------------   Component Test Result  (Quality)

4. (b) Build --------------------------------------   Assembly Test Result (Quality)

5. (a) Test ---------------------------------------   System Integration Test Result Report (Quality)

5. (b) Test ---------------------------------------   User Acceptance Test (Quality)

6. Release and Deploy ---------------------------   Project Performance Report

 

 

SAS DI Certification Notes For A00-260

If you are preparing for SAS DI Certification (A00 -260), the following notes could help you to clear it

• For register table wizard in SAS Data Integration Studio, Metadata for the selected physical table or tables would be stored in the specified SAS folder location which is specified in the wizard


• If we register the metadata for an ODBC data source, it would involves registering a server definition that points to the ODBC data source and a library accessing this server definition


• SAS Data Integration Studio is dependent on an administration function which is setting up of SAS Application Servers


• The ability to deploy a SAS Data Integration Studio job as a web service or a SAS Stored process requires an additional set up that would be performed in SAS Management Console


• The metadata for the library tables is NOT defined as a part of new library wizard


• Use the New User Written External file wizard to register an external file with the following structure like : First, Second, Third and fourth line contains following information respectively : First name, Last name, Address and Phone number


• In SAS DI Studio, COBOL Copybook is NOT an available option from the file - new menu choice under External file grouping


• System DSN is not specific to an individual user, Anyone with permission to access the data source can use it


• The Return Code check transformation can be added to the job flow immediately following the Extract and Sort transformation - The Status handling tab in each of the Return Code Check Transformations properties can then establish the desired status handling


• While writing postcode in the Precode and Postcode tab of the Transpose Transformation in SAS DI Studio &SYSLAST allows us to reference the transformation output table regardless of the actual physical name for the target table


• Ampersand Sign (&) on the top left corner of any transformation denotes that, that object has a defined parameter


• With the help of Data Validation Transformation, we can create a job that checks condition for our data before the data would be loaded into a data warehouse. This job should be able to  detect error conditions such as missing data or duplicate data and take appropriate action like registering error conditions in log etc.


• In SAS DI Studio, we can create three type of expression by using the Expression Builder window in Where Tab of SAS Extract Transformation which are : SAS Expression, SQL Expression and a Constant