1. SeETL Demonstration 03 Using the Runtime Engine 1/3/2012 www.InstantBI.com

2. Introduction  History of the SeETL Engine  The innovation to C Generation  The innovation to C++/ODBC  Demonstration of C++/ODBC engine  Summary

3. History of the SeETL Engine  1995 – Cobol templates created, customised by hand  1997 – Cobol templates parameterised and cobol programs generated  1998-2002 – No activity  2002 – C Data Warehouse Generator created  Generated C code rather than cobol code  2003 – Migration from C and embedded SQL to C++ and ODBC 3.5.1  2004 SeETL Design Time to generate views needed  2008 – SQL Generation version invented  2009 – A major client asks us to massively expand the coverage of the dictionary.

4. Innovation to C Generation  In 2002 Ralph Kimball suggested I write and article on what good ETL engines would have in them  Ralph moved on and the article was not printed  The list of features made compelling reading  Cobol was dead by this time so a migration to C with embedded SQL that emulated the cobol was attempted  It was successful and I learned a great deal about writing C with embedded SQL  The C data warehouse generator was released in 2002  Interest was very mild and no sales ensued

5. Innovation to C++/ODBC Engine  In 2002 MSFT announced it would remove embedded SQL in C from SQL Server 2005 forwards  After 2005 ODBC was the ONLY interface solution for ETL  The article for Ralph was still on my mind  Question  “Could I write the ETL tool I wanted?”  In late 2002 the answer was “yes”  I had developed the base classes that would be necessary to develop the remainder of the C++ engine  Version 1.0 was released in 2003 to warm response  Three good sales ensued over the next year or two  The C++ engine was used and further developed on projects  It is very stable and robust

6. Demo of C++/ODBC Engine  We will show you just a simple set of ETL generation

7. Summary  History of the SeETL Engine  The innovation to SQL Generation  Demonstration of SQL Generation  Summary