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 _at_ Nationwide Building Society
• Experience 15yrs IT, 11yrs SQLServer
• Blog http//sqlmunkee.blogspot.com
• Twitter _at_sqlmunkee
• Mail SQLMunkee_at_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
ltpresentation1gt
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
Feature SSIS SDS
ETL Operations Yes Yes
Sharing No Yes
Wide range of standard objects Yes No
Custom objects Yes Yes
Standalone development Yes Yes (but)
TryCatch Custom Built-in
Metadata and Lineage No Yes
Push down WTF ? Yes
Script support Yes Yes
Script Language VB.net / C (2008) Python
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,
  TryCatch, 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
lt/presentation1gt
13
ltpresentation2gt

• 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
19
(No Transcript)
20
(No Transcript)
21
(No Transcript)
22
(No Transcript)
23
(No Transcript)
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 youre 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 cant 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 youll have one DSMC per landscape unit

28
(No Transcript)
29
(No Transcript)
30
I hope theres a WhiteBoard

• Shall we draw some pictures of what it might look
  like ?

31
lt/presentation2gt
32
Comfort Break

• If we havent already had one..

33
ltpresentation3gt

• Lets go look see

34
lt/presentation3gt

• Questions ?

35
GOTO Pub()