SAP
Replication Server:
·
Log based Database replication tool
SAP
Sybase Replication server Intro:
·
Transactional data movement product that moves
and synchronizes data across the enterprise
·
Real-time business intelligence
·
Zero operational downtime
·
Log based replication process
·
Non-intrusive
·
Very high performance
·
Improve recovery, resumption times and minimize
downtime
·
Bi-directional replication
·
Standby DB is always available and can be used
for read-only report server
·
Fresh data to enable timelier decision
·
Run resources intensive reports on reporting
servers without implacting OLTP systems
·
Reduces info latency for reporting and optimize
batch reporting
·
RT data sharing and synchronization
·
Facilitates decentralized business operations
·
Enables remote application to access data locally
for improved performance
Relies on
log based replication techniques:
·
Changed
Data Capture
·
not done against the data volume of the source
database
·
reads directly the database log
·
reduces the workload that the replication
process brings to the source db
·
Data distribution and migration
·
Distribute: move centralized data to ops apps
·
Share data between ops apps
·
Synchronize: maintain consistency in overlapping
data values
·
Migrate: move from older versions of database
platform to newer
·
Real time decision support
·
Create ops data store
·
RT loading of DW (HANA< SAP IQ<SAP ASE, Oracle,
Microsoft, IBM)
·
RT data sharing and synchronization
·
Enable bzn continuity in case of site wide
disaster
·
Maintain app availability during
planned/unplanned downtime
Source
system = Primary DB
Target =
Replicate DB
SAP
replication server:
·
Heterogenous materialization( initial load)
·
Pre-req before you can replicate transactions
·
Optimized for numerous tables and big data
volumes
·
Leverages native HANA ODBC driver
·
Strong bulk insert/delete capabilities
A. in transaction LTR in SAP Landscape Transformation (SLT)
B. in the Import dialog of the Quick Launch of SAP HANA studio
C. in transaction SAP ERP Tables and Indexes Monitor (DB02)
D. in the Data Provisioning dialog of SAP HANA studio
2) SAP HANA Appliance Software :
a) SAP HANA Studio = SAP HANA Load Controller
b) Sybase Replication Server = SAP Host Agent
c) SAP HANA Database Clients = LM Structure Files
d) SAP HANA Database = SAPCAR
3) SAP HANA Enterprise extended edition : (For Log based replication)
i) Sybase Replication Agent
ii) Sybase Replication Server
iii) SAP HANA Load Controller (R/3 Load in Source + R/3 Load in SAP HANA)
5) Replication Methods Overview :
a) Source System-SAP ERP (Application Layer) à Trigger Based Replication à SAP In-Memory Database
b) Source System-SAP ERP (Application Layer) à ETL Based Replication à SAP In-Memory Database
c) Source System-Database (Log File) à Log Based Replication à SAP In-Memory Database
RFC connection is required for connection from Replication server to HANA Database : False
- HANA is connected to ERP systems, Frontend modeling studio can be used for load control and replication server management
- HANA Supports Sybase Replication Server – Sybase Replication Server can be used for real time synchronization of data between ERP and HANA
- Replication servers create tables in column store per default
- A “What-if” scenario is the strength of SAP BO Dashboards.26) a) SAP ERP à SLT (Replication Server) ----(Real Time Replication) à SAP HANA à SAP BO à Presentation
C) SAP HANA Appliance (SLES 11 SP1)
i. SAP HANA Database – Clients Studio
ii. SAP HANA Load Controller
iii. SAP Host Agent 7.20
iv. Sybase Replication Server 15.5 + ECDA