SAP Data Services

1. SAP Data Services The Future Of Enterprise ETL ?

2. Housekeeping • Venue • Tea / Coffee • Comfort Break (maybe) • Presentations • Duration • Questions welcome

3. Speaker Bio • Richard Munn • DBA @ Nationwide Building Society • Experience: 15yrs IT, 11yrs SQLServer • Blog: http://sqlmunkee.blogspot.com • Twitter: @sqlmunkee • Mail: SQLMunkee@gmail.com • Social status: Northener

4. Presentations • 1 - Quick comparisons between SSIS and SDS • 2 - Overview / Explanation • 3 – Demonstration (I hope) • Knowledge of SSIS / ETL terminology is assumed • Disclaimer

5. <presentation1>

6. SSIS vs. SDS Paradigm Shift ?

7. The Future Is Yellow • SAP Data Services (SDS) is an Enterprise Solution for ETL. • Platform agnostic • Repository based ETL development. • Any object can be shared (I think) • Supports CheckOut /CheckIn usage

8. Comparisons

9. Job Execution • SSIS just requires a command line (DTExec) • SDS (even in development) needs: • A job to contain Workflow / Dataflow • A job server to execute the job • More infrastructure is required to provide service

10. Restartable Jobs • Must be hand-crafted in SDS • Complex logic required with multiple Workflows, Try…Catch, Parameters, Variables, etc… • Built-in with SSIS

11. Challenges • Requires dedicated, experienced developers and support staff (IMHO) • Does the job in a controlled and ordered manner. • Not as “user-friendly” as SSIS.

12. </presentation1>

13. <presentation2> All aboard the big yellow fun bus !

14. Key Elements • Repository / Repositories • Data Services Designer • Job Server / Server Group • Management Console

15. Repositories (1) • Somewhere to store your objects: • Projects • Jobs • DataSources • DataFlows • WorkFlows • Transforms More on these later…

16. Repositories (2) • 4 types: • Local - Held on a local DBMS • ‘Personal’ * - Work in progress • Central - Items to be used / shared • Secure - Only Admin access (this can be a problem) * - not an SAP option, more ‘best practice’

17. Data Services Designer • Local installation of Development Environment for creating the objects to store in the Repository • …but can be delivered over Citrix or Softgrid/AppV • Fairly simple in look and feel, but actually quite complex • Would anyone like to take a look ?

18. Starting The Designer

24. Jobs (1) • Anything you want to do is treated as a ‘job’ in SDS • Jobs usually contain WorkFlows and DataFlows (but you can have one without the other, unlike SSIS) • 2 types: • Batch Job • Real-Time Job

25. Jobs (2) • Batch Job • Commonly single unit-of-work • Overnight / Off-peak ETL processing • Real-Time Job • Creates a Web service • Typically 3Flow/2Transform data movement • Simple operations ONLY please

26. Job Servers • Actually runs your job (even if you’re moving data about locally) • Multiple Job Servers can function as a “Server Group” • Server Groups share the submitted jobs between them, but once a job starts it can’t move servers (ask me about this)

27. Management Console • Single point of administration for… • Users • Job Servers (reporting) • Repositories • Browser-based, so requires Apache Tomcat (later versions support other web servers like IIS) • Typically you’ll have one DSMC per landscape unit

30. I hope there’s a WhiteBoard… • Shall we draw some pictures of what it might look like ?

31. </presentation2>

32. Comfort Break If we haven’t already had one..

33. <presentation3> Let’s go look see…

34. </presentation3> Questions ?

35. GOTO: Pub()