Replication vs. Extraction
| |
Replication vs. Extraction |
| Key Points |
- Effective reporting from SAP will require either data extraction or replication
- Replication wins over Extraction
- Problems with Extraction:
extraction loads, overnight shutdowns and batch processing, resource load competes with transactional/operational needs
- Benefits of Replication:
real time reporting, no load on transactional/operational system, no shutdowns, no batch processing, reporting data always in synch
|
Some companies are wary of any solution involving data replication.
Insight: The word "replication" carries heavy baggage - but shouldn't.
In the past, replication has meant a very large project with attendant costs and time commitments. Professionals who’ve experienced that type of replication project have no interest in more replication of data, and more SAN and data storage costs. However, today’s replication offers vast improvements over that of yesteryear.
For reporting purposes, data will either need to be extracted from SAP or replicated. Replication offers inherent benefits not attainable with extraction. In the modern world, replication is a thing of beauty that provides the underpinning for data liberation. This means a new world of fast, flexible, real-time reports.
Problems with direct reporting against R/3 or extracting data from R/3
- Not practical to report directly against R/3 instead of a data warehouse, because of the strain on R/3.
- Extraction doesn't support real time reporting – as SAP states, you should wait at least 2 hours from data entry until you run extraction.
- Batch extractions may require system shutdown, meaning once per night updates of the reporting data warehouse.
- With extraction, the so-called best practice is to re-extract all data every night because there is no reliable way to call the Delta.
- ABAP extractors must call entire tables, so the load cannot be trimmed to only call data of interest for reporting.
Why replication provides a better data foundation than extraction.
- With modern databases and architecture, replication can be incremental and scalable – not an all-or-nothing project.
- Modern replication is elegant, easy and extremely cost effective. When evaluated, it's the clear winner over extracting to the SAP Business Warehouse.
- Instead of batch processing and extraction loads, the SDL "listens" to the data replication feed that is native to the database used in conjunction with the SAP productive instance.
- Changes in R/3 records show up immediately in the Simplement Data Liberator – this enables real-time reporting.
- The Simplement replication process puts NO burden on SAP R/3 – meaning it will perform better.
- The data liberated by replication is available even when SAP is shut down.
|