SeETL Demonstration 07 SQL Statement Processing 1/6/2012

Introduction  Why have complex SQL Statement Processing  The Loading Worksheet  Demonstration of SQL Processing  Demonstration of reports  Summary

Why Have SQL Processing  In early versions sql statements were simple  Simple truncates, deletes, inserts selects  Logging for these statements was minimal  With SEL ETL Generation we have long sql statements  The existing sql statement processor was not adequate  An existing client also wanted the SQL in the database for better audit, security, control etc  We wrote a load processor for files to be placed into a new data dictionary table  We wrote a statement processing program to accept a file name but retrieve the actual SQL from the specified dictionary  This means 100% of the ETL can be SQL inside the database. Far more robust. Far more reliable.

Demonstration  Demonstration of the workbook  Demonstration of the statements inside the dictionary  Demonstration of the statement processing

Summary  Why have complex SQL Statement Processing  The Loading Worksheet  Demonstration of SQL Processing  Demonstration of reports  Summary