Coding efficiency is generally measured in CPU time, disk space or memory usage. This is perfectly reasonable for SAS code that will be submitted many more times than it will be updated. However, there are coding environments where SAS programs are being written for single production runs, and then adapted and updated for different production runs, e.g. in clinical development. In these cases a new measurement of maintenance time may be more important.
This paper discusses the choices that need to be made when coding efficiently in different types of SAS programs, each illustrated by coding examples.
- PhUSE, Dublin, Eire – 9th October 2006 (Best Presentation in Tutorials)
- Wisconsin Illinois SAS Users Conference, Milwaukee, WI, USA – 22nd June 2007
- PSI Statistical Computing SIG, Macclesfield, UK – 3rd September 2007
- PhUSE Single Day Event, Basel, Switzerland – 28th May 2008
- PhUSE Single Day Event, London, UK – 11th June 2008