Staging area design for SAP Data services

[#1]

Hello Experts,

I am using SAP Data services and would like to know if I can do the whole ETL (extracting the source tables, transforming, validating and enriching) in one single database on the server instead of creating multiple databases like landing DB for extraced tables, staging table for transformed and so on...

Please let me know if you know of pros/cons of single DB approach. My question is why to oversimplify something (i.e. splitting the DBs) if it can be done in one DB. Also we have separate environments for Dev, Q and Prod and that categorization is already there.

dirk.venken arun.sasi scott.broadway

[former_member187605]

i always prefer to have all data in a single database. In HANA, Oracle, DB2, Teradata...you can separate from target data at schema level. In a less powerful dbms, lke MS SQL Server, SQL Anywhere... create separate staging and target databases.

[Mageshwaran_Subramanian]

I would suggest a single DB or single shema if you follow the proper naming convention to differentiate source and target tables. It would make DBAs job easier in terms of maintenance.