You're reading from Mastering SAS Programming for Data Warehousing An advanced programming guide to designing and managing Data Warehouses using SAS

Product type Paperback

Published in Oct 2020

Publisher Packt

ISBN-13 9781789532371

Length 494 pages

Edition 1st Edition

Tools

SAS

Concepts

Application Development

Author (1):

Monika Wahi

Preface

1. Section 1: Managing Data in a SAS Data Warehouse

2. Chapter 1: Using SAS in a Data Mart, Data Lake, or Data Warehouse FREE CHAPTER

3. Chapter 2: Reading Big Data into SAS

4. Chapter 3: Helpful PROCs for Managing Data

5. Chapter 4: Managing ETL in SAS

6. Chapter 5: Managing Data Reporting in SAS

7. Section 2: Using SAS for Extract-Transform-Load (ETL) Protocols in a Data Warehouse

8. Chapter 6: Standardizing Coding Using SAS Arrays

9. Chapter 7: Designing and Developing ETL Code in SAS

10. Chapter 8: Using Macros to Automate ETL in SAS

11. Chapter 9: Debugging and Troubleshooting in SAS

12. Section 3: Using SAS When Serving Warehouse Data to Users

13. Chapter 10: Considering the User Needs of SAS Data Warehouses

14. Chapter 11: Connecting the SAS Data Warehouse to Other Systems

15. Chapter 12: Using the ODS for Visualization in SAS

16. Assessments

17. Other Books You May Enjoy

Questions

Why is it helpful to consider both analyst and developer users in a data warehouse or data lake?
Why do analyst users of data lakes and developer users of data warehouses need extensive documentation on source datasets?
What are the pros and cons of having analysts access a data lake server directly?
How does having multiple foreign keys in a data warehouse make it more useful to analysts?
Imagine you are hosting an annual dataset in your data warehouse. One year when you receive the dataset, you learn that a new additional categorical variable is included that you find valuable, named ADJPRICE. For the next 2 years, you receive the dataset with ADJPRICE in it coded according to the same system, but the third year, you receive the dataset without ADJPRICE but with ADJPRICE2, which is coded slightly differently than ADJPRICE. If you were to make a crosswalk variable to handle ADJPRICE and ADJPRICE2 in datasets over all these years, what coding would it...