Hi,
Recently with HANA SPS9 we have now another option to replicate tables into HANA systems which is the SDI (Smart Data Integration) residing
and running on the HANA systems.
I already heard some people asking if the SLT replication will no longer be required, if we can move/migrate all our replication tables using SLT and BODS into the SDI option, etc.
I’ve been working with SLT for real time replication since its beginning and I just now I have the feeling that SLT as replication tool is getting to a mature point, meaning it’s more solid now as replication solution tool, offering more options and functionalities to deal with real time replication tables, and having less and less bugs.
I’ve been reading about the SDI option for replication, which looks very promising. I guess its strongest sales pitch is that avoids having a BODS or SLT system, meaning, less systems to build in my infrastructure, lower cost. Aside SDI runs on SAP HANA which always has plenty of CPU and RAM.
Now, what is not clear to me is if SDI can really handle really big tables, constantly changing, real time replication? The documents I’ve read I don’t see where I can set the table partition for the replication, performance and initial load options that we have in SLT LTRS rules. Does anybody know where I can use such options on SDI when replicating new big tables? The examples in the documentation and videos are always using tiny tables that does not reflect the majority of customers that use SAP HANA, where the tables, or main ones that are replicated, are usually massive tables.
SLT Replication vs SDI Smart Data Integration? For real time replication of lot of tables, really big tables, with rules, extra fields. What is the best option?
Can at this point SDI take over all the current replication running on SLT and BODS systems?
Thanks
Rod Cardenas