SAP HANA Smart Data Access: Modeling Recommendations
Showing posts with label sda. Show all posts
Showing posts with label sda. Show all posts
Tuesday, 7 June 2016
Thursday, 2 June 2016
What’s new in SAP HANA SPS12 – Smart Data Access
Overview
The SPS12 release is upon us, and with it a few great new features for SDA: Kerberos constrained delegation, UPSERT support, ROW_NUMBER support, performance optimizations and more.
What is SAP HANA Smart Data Access?
For those of you not so familiar with SDA, it has been available as a part of SAP HANA since SPS6 and gives you the power to expose data from remote sources as virtual tables in SAP HANA. This is a huge advantage compared to traditional ETL processes in many situations as it is gives you a cost-efficient, easy-to-deploy option to get real-time data visibility across fragmented data sources. Not to mention the advantage it brings in terms of location agnostic development when building applications on HANA which need to leverage data from multiple sources.
The SPS12 release is upon us, and with it a few great new features for SDA: Kerberos constrained delegation, UPSERT support, ROW_NUMBER support, performance optimizations and more.
What is SAP HANA Smart Data Access?
For those of you not so familiar with SDA, it has been available as a part of SAP HANA since SPS6 and gives you the power to expose data from remote sources as virtual tables in SAP HANA. This is a huge advantage compared to traditional ETL processes in many situations as it is gives you a cost-efficient, easy-to-deploy option to get real-time data visibility across fragmented data sources. Not to mention the advantage it brings in terms of location agnostic development when building applications on HANA which need to leverage data from multiple sources.
Tuesday, 31 May 2016
Modelling Learning Double Action or two things I just learned about modelling in SAP HANA SPS 11
The scenario in mind here was a SAP BW on HANA system reading data from a Suite on HANA system and using the SAP HANA live content installed there.
The Open ODS feature of SAP BW on HANA was to be used here as it allows reading from tables and views exposed via SDA in the local SAP HANA instance.
Now this idea sounds splendid.
Instead of having to manually build an extractor or an data export database view (both of which can be extensive development efforts), why not simply reuse the ready made content of SAP HANA live for this?
As usual the proof of the pudding is in the eating and as soon as it was tried out a severe shortcoming was identified:
The Open ODS feature of SAP BW on HANA was to be used here as it allows reading from tables and views exposed via SDA in the local SAP HANA instance.
Now this idea sounds splendid.
Instead of having to manually build an extractor or an data export database view (both of which can be extensive development efforts), why not simply reuse the ready made content of SAP HANA live for this?
As usual the proof of the pudding is in the eating and as soon as it was tried out a severe shortcoming was identified:
Sunday, 3 January 2016
Smart Data Access - Basic Setup and Known Issues
Purpose
This blog will focus on basic setup of Smart Data Access (SDA) and then outline some problems that customers have encountered. Some of the issues outlined in the troubleshooting section come directly from incidents that were created.
There is already a lot of information on Smart Data Access which this blog does not aim to replace. Throughout the blog, I will reference links to other documentation that can cover the topics in more detail.
What is Smart Data Access (SDA)?
SDA allows customers to access data virtually from remote sources such as Hadoop, Oracle, Teradata, SQL Server, and more. Once a remote
connection to a data source is done we can virtually connect to the tables and query against is or use in data models as if it were data that resides in a SAP
HANA database.
This allows it so customers do not have to migrate or copy their data from other databases into a SAP HANA database.
How to Setup SDA?
Smart Data Access was introduced in SAP HANA SP6, so if you intend on using SDA be on at least this revision.
Prior to connecting to a remote database you will need to configure an ODBC connection from the server to the remote database. For
assistance on how to install the Database drivers on how to install the database drivers for SAP HANA Smart Data Access please refer to SAP note
1868702 and refer to the SAP HANA Learning Academy videos
https://www.youtube.com/watch?v=BomjFbJ25vo&index=16&list=PLkzo92owKnVx_X9Qp-jonm3FCmo41Fkzm
This blog will focus on basic setup of Smart Data Access (SDA) and then outline some problems that customers have encountered. Some of the issues outlined in the troubleshooting section come directly from incidents that were created.
There is already a lot of information on Smart Data Access which this blog does not aim to replace. Throughout the blog, I will reference links to other documentation that can cover the topics in more detail.
What is Smart Data Access (SDA)?
SDA allows customers to access data virtually from remote sources such as Hadoop, Oracle, Teradata, SQL Server, and more. Once a remote
connection to a data source is done we can virtually connect to the tables and query against is or use in data models as if it were data that resides in a SAP
HANA database.
This allows it so customers do not have to migrate or copy their data from other databases into a SAP HANA database.
How to Setup SDA?
Smart Data Access was introduced in SAP HANA SP6, so if you intend on using SDA be on at least this revision.
Prior to connecting to a remote database you will need to configure an ODBC connection from the server to the remote database. For
assistance on how to install the Database drivers on how to install the database drivers for SAP HANA Smart Data Access please refer to SAP note
1868702 and refer to the SAP HANA Learning Academy videos
https://www.youtube.com/watch?v=BomjFbJ25vo&index=16&list=PLkzo92owKnVx_X9Qp-jonm3FCmo41Fkzm
Subscribe to:
Posts (Atom)