Author: DaFRK

There are now a variety of integration technologies to data in your SAP HANA to get instance. The technical term for the transmission of data in an SAP HANA is instance of "SAP HANA data provisioning". Second to enumerate a small pool of available technologies, about the data services (DS) were HANA direct Extractor connection (DXC), SAP, smart data access (SDA), SAP LT replication server (SLT), SAP replication server (SRS, formerly Sybase), SAP HANA system replication, the HANA cloud connector u. v. m. In this post we want explicitly SAP HANA smart data integration (SDI) devote, however the Einstazzweck of this technology only are set, if we first deal with the current data replication portfolio of SAP. What types of replication technologies are there? When replicating data in an SAP HANA database you categorized the available replication technologies as follows trigger-based replication is used, for example, from the SAP server LT replication. The replication technology installed trigger. Replication Server at the database level, which run in the case of the LT when executing certain SQL statements (INSERT INTO, UPDATE, DELETE). This trigger signal the LT replication server then, that something in the database table to be replicated has changed in the source system. The LT replication server checks then so-called logging tables in the source system to the changes and "repeated" only the Delta to the current database in the target system then by the source system. That is trigger-based technology minimizes the amount of data to be transferred before the transport, which is one of the main advantages of trigger-based replication. Thus this type of data replication so excellently suitable for near-real time data replication, the almost real-time transfer of data to a target system. ETL-based replication is used, if the data from the source system before transferring it to the target system (your SAP HANA instance) into a destination format must be converted, because such is the number of attributes or Changes table columns in the destination table, or the data type of a column. Even if able to do so is, for example, the LT replication server perform simple transformations on table content before it's transferred, you should use rather dedicated proposed technologies for this purpose. Often this type of replication is used to load data of specific business periods of multiple systems for analysis purposes in a HANA. Extractor-based data transfer is pretty straight-forward simple extraction of data and the subsequent import of data models in SAP HANA. The technologies proposed by SAP as the DXC extracted the data already in a SAP HANA matching destination format. The manual process of transformation reduces to a minimum. When do I use which transmission technology for SAP HANA? If you specifically ask, when you should use what integration or replication technology for SAP HANA, maybe this chapter is a short way way for you. Specifically has for example used a certain strength, and thus an optimal scenario in which it is used, so any integration technology the LT replication server for trigger-based real-time replication of table content (this is not object-oriented). By trigger-based replication is the volume of data to be transferred at the outset reduces. But be careful: the replication of the LT replication server is not object-oriented or transaction-oriented. That means if you about for a "purchase order" the contents of four different tables from the source system must replicate, can it be that the contents of 2 tables at the point X in the target system has arrived, but the content of the other four tables not yet. The LT replication server is so not transaction-oriented, but transmits only the contents of a table in each replication cycle. Here therefore you have no warranty on object-oriented consistency in the target system. Either live with this uncertainty in the target system or use an object-oriented replication, for this kind of Daten.Derzeit the SAP is working on the implementation of the object-oriented replication for the LT replication server, but for SAP objects. For non-SAP objects you must make an effort at present a different technology or your own application logic between the switch. the HANA cloud connector to the unique copy of stack from database tables in a HANA instance in the cloud. Of course, it is possible to transfer data to replication server in a HANA-cloud instance for example in real time about the LT. The HANA cloud connector is only an alternative for batch transmission of data at low cost (low TCO) in effect. If you so need your data in real time, but only intermittently in your target-HANA, HANA cloud connector the technology of your choice. the SAP replication server use, in contrast to the SAP LT replication servers, if you need transactional consistent data replication. SAP Replication Server provides so in contrast to the SAP LT replication server, make sure that changes a database is replicated so as you are changed within a database transaction. Become so within a database transaction (in the SQL statement about what happens to a "commit") changes to, for example, 5 tables connected with each other by foreign key relationships are written are updated in the SAP replication servers all these 5 tables at the same time. This means: Here you have in contrast to LT replication server about your "purchase order" always consistent at the point X in the target system. The disadvantage of this is that replication server for this purpose each transaction individually must transfer the SAP ergo, that replication server must shoveling much more data about the management of SAP as the LT replication no matter in terms of transaction happened how much in between servers replicating only the current state of a table. Another advantage of transactional-oriented data replication is that you can restore the target database exactly so finely granular point in time recovery as the source database. That is when in the source database was accidentally overwritten a data set with incorrect information and they need to recover the old data status of this record just a point in time recovery run in the target database to the last consistent state, and then export the data in the source database, to restore the desired level. That would be an LT with a replication server replicated database cannot (or luck). You use the SAP HANA system replication, if you need transactional replication, source and target system but on both sides of an SAP instance of HANA. That means while with the SAP replication server is usually an AnyDB the source system to bind it in the SAP HANA system replication as a source system also a SAP HANA's database. The SAP HANA system replication has in contrast to the SAP replication server, the advantage is that the HANA to HANA transmission optimized for you and in addition to the mere data yet, for example, the system configuration, HANA database user and other HANA objects such as calculation views etc. can replicate. If you want to learn more about the SAP HANA system replication, read my post on SAP HANA tailored data center integration (SDI). What are typical use cases for the different SAP HANA data provisioning technologies? The SAP LT replication server. The SAP is LT replication server, as we have learned, an object-oriented or not transactional data provisioning technology. Because, for example, a transactional consistency must be ensured in financial accounting systems, LT replication is the SAP server so, for example, for the live transmission of financial data to two locations, if at any time a transactional consistency in source and target is necessary. The SAP LT replication server is often used for scenarios in which he can shine. The "LT" in the SAP LT replication server is for landscape transformation. That is the main Einstazzenario of SLT is the consolidation of multiple SAP application systems of the same type in a single system to tighten the system landscape. As LT replication used server as often the SAP, to merge several company codes. This transforms the LT replication server fields of the tables of a company code in the other and thereby replicates the data under the new company code in the target system. Since the SAP LT Replication Server provides no transactional consistency, should do this in both systems downtime planned are. That is not bad but because this consolidation is made of systems already mostly in the context of a migration or an upgrade to a new release. Thus, a downtime window was so from the outset firmly planned. Furthermore suitable SAP LT replication server to optimally for the consolidation of data from multiple sources to a target, to make available for analytical purposes or to provide a search based on data from multiple systems. Because often no transactional consistency is assumed here. Instead, just at the time X the objects analyzed or displayed in the search results image precisely replicated. It accepts the user aware the severity through at the time X still not complete objects that can not be displayed replicated or Analysis can not included in that. Often such as data lakes are built with SLT SAP data for analysis software QlikView, Lumira and Tableaut or make it available to search engines. When and how does SAP HANA smart data integration (SDI) in the game? SAP HANA smart data integration is a huge buzzword in the SAP world. The trade fairs fusslig talk to the mouth. What is behind this prodigy? SAP HANA smart data integration aims to combine the advantages of the above different tools for HANA-optimized Einsatzzenarien. Simply put: the above presented data provisioning technologies will continue to have their raison d ' être in scenarios in which they particularly shine (about the merging of company codes with SAP LT replication server or ensuring the high availability of SAP HANA instance through the...

Author: DaFRK

SAP HANA smart data integration and other HANA provisioning tools at a glance

Recent Posts

Recent Comments

Archives

Categories

Meta