What’s New in SAP HANA 2.0 SPS 01 smart data access

This blog will cover the SAP HANA smart data access (SDA) highlights of the SAP HANA 2.0 SPS 01 release. New with this release is support for the export/import of virtual tables, enhancements to the SAP HANA smart data access cockpit tile, release of the new linked database feature, and enhancements to our Hadoop integration.

Export/import of virtual tables

The new export/import of virtual tables feature will give our users the ability to transport virtual table metadata between DEV/QA/PROD system landscapes, meaning that virtual tables no longer have to be created in all environments manually.

Image 1: Export/import of virtual tables

The transportation workflow is greatly simplified and users have the option to RENAME REMOTE OBJECT to easily connect to a new productive remote source. To transport virtual tables from one system to another follow these steps:

  1. Export the virtual table schema into directory “/tmp/” in the source system
  2. Create the remote source in the target system before importing the virtual tables
  3. Run the IMPORT function in the target system*

* To change the location or name of the remote object, use the RENAME REMOTE OBJECT function when importing the virtual table schema

Please note that the RENAME REMOTE OBJECT option is intended to change the database name and the schema name of the remote location, but not the remote object itself.

Cockpit tile enhancement

New with SAP HANA 2.0 SPS 01 is a count of running statements and active connections right in the overview SAP HANA smart data access tile.

Image 2: SAP HANA smart data access cockpit tile

By clicking on the running statements view or active connections view, users will be able to see what remote statements are running or have recently ran, as well as monitor remote connections and their status.

Linked database

The new linked database feature allows users to directly access remote tables and views without having to manually define virtual tables. Once the remote source is added users will have the ability to perform DML queries directly against remote tables using three part names (remote_source.schema.table). To query the remote source, users will need to be granted the LINKED DATABASE privilege. Currently this feature is only supported for SDA connections from SAP HANA to SAP HANA.

For more information on linked database, read the introduction to linked database blog or refer to the SAP HANA administration guide.

Hadoop integration

In the Hadoop integration space, we have added a few notable enhancements for this release. We have extended DLM support by adding support for synonyms (.hdbsynonym) for declaring remote destinations using CDS, we have enabled data movement from SAP HANA extended tables to Hadoop, as well as added support for different file formats in Hadoop.

Image 3: SAP HANA Hadoop integration overview

Additionally, we now support SAP Cloud Platform Big Data Services (formerly Altiscale) for connections with the SAP HANA Spark Controller 2.1. Lastly, we have enabled support for inserts into SAP Vora tables for connections via the SAP Vora adapter. For more information on SAP HANA Hadoop connectivity please refer to the SAP HANA administration guide.

 

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Shailesh Moholkar

    Dear Aleks,

    We are working on Data Virtualization layer (DVL)  solution for one our customers. We are exploring HANA  Virtual tables to connect to “READ” data from all the sources .  say SAP CRM, SAP ECC and also Hadoop.

    I read that Virtual tables wont work in multi node cluster in HANA ( though they are old post , didnt see any which says this limitation is overcome in the new releases) My customer has a Multi Node installation.

    Also , When we want to read the data directly from the source for a Report/query. How is the master data handled . or we should connect to MDM system also as one source ( they have IBM MDM) . Will this not affect the performance . or is this the way it needs to be used for a DVL scenario?

    We have teams working on different solutions ( Deenodo, Composites etc ) I am looking into SAP HANA DVL  solution.  Can you please clarify these points , greatly appreciated!

    Thanks and kind regards,
    S

     

    (0) 
    1. Shailesh Moholkar

      One more point !

      I am also thinking of the newly released Linked Data Base concept. The SAP suite is going on HANA , so HANA to HANA should work there as per your blog. Is it too early to start using this feature for a full blown DVL solution.

      Important : I am recommending  DVL solution only for realtime/operational reporting . For strategic / huge historical data computation I would still prefer a EDW with Data Mart layer. Correct me if this is wrong understanding .

      Thanks in advance for your time !

      Thanks and kind regards,

      S

       

      (0) 

Leave a Reply