SAP Data ServicesThe Future Of Enterprise ETL ?

HousekeepingVenueTea / CoffeeComfort Break (maybe)

PresentationsDurationQuestions welcome

Speaker BioRichard MunnDBA @ Nationwide Building SocietyExperience: 15yrs IT, 11yrs SQLServerBlog: http://sqlmunkee.blogspot.comTwitter: @sqlmunkeeMail: SQLMunkee@gmail.comSocial status: Northener

Presentations1 - Quick comparisons between SSIS and SDS2 - Overview / Explanation3 Demonstration (I hope)

Knowledge of SSIS / ETL terminology is assumedDisclaimer

SSIS vs. SDSParadigm Shift ?

The Future Is YellowSAP Data Services (SDS) is an Enterprise Solution for ETL.Platform agnosticRepository based ETL development.Any object can be shared (I think)Supports CheckOut /CheckIn usage

Comparisons

Job ExecutionSSIS just requires a command line (DTExec)SDS (even in development) needs:A job to contain Workflow / DataflowA job server to execute the job

More infrastructure is required to provide service

Restartable JobsMust be hand-crafted in SDSComplex logic required with multiple Workflows, TryCatch, Parameters, Variables, etc

Built-in with SSIS

ChallengesRequires dedicated, experienced developers and support staff (IMHO)Does the job in a controlled and ordered manner.Not as user-friendly as SSIS.

All aboard the big yellow fun bus !

Key ElementsRepository / Repositories

Data Services Designer

Job Server / Server Group

Management Console

Repositories (1)Somewhere to store your objects:ProjectsJobsDataSourcesDataFlowsWorkFlowsTransforms

More on these later

Repositories (2)4 types:

Local - Held on a local DBMSPersonal * - Work in progressCentral - Items to be used / sharedSecure - Only Admin access (this can be a problem)

* - not an SAP option, more best practice

Data Services DesignerLocal 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 ?

Starting The Designer

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 JobReal-Time Job

Jobs (2)Batch JobCommonly single unit-of-workOvernight / Off-peak ETL processing

Real-Time JobCreates a Web serviceTypically 3Flow/2Transform data movementSimple operations ONLY please

Job ServersActually 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)

Management ConsoleSingle point of administration forUsersJob 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

I hope theres a WhiteBoard

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

Comfort BreakIf we havent already had one..

Lets go look see

Questions ?

GOTO: Pub()