Index Server is heart of SAP HANA system and is responsible for processing all SQL statements sent to HANA database. This server contains SQL/MDX Processing engine that is responsible to process and analyze data in HANA db.Index Server also contains Persistence layer for scalability and restoration of the system. In case of system failure, power failure or database corruption, Persistence layer is responsible for the restoration of HANA system to last save point.When you are running complex and large calculations, and there is a system failure Persistence layer is used to ensure that transactions are either fully executed or complete ... Read More

Each HANA system contains multiple serves inside, which are responsible to perform different functions. Index Server is heart of SAP HANA system which contains SQL/MDX processor for handling SQL statements. Key component includes −Index ServerPreprocessorName ServerStatistics ServerHANA XS EngineSAP Host AgentSAP Solution Manager Diagnostic AgentSAP HANA Studio + RepositorySAP HANA Software Update Manager SUM

You can use following SQL statement for this −CREATE VIRTUAL TABLE ExampleCREATE VIRTUAL TABLE ABC.test_VT AT “ORCL_11G_WIN”.”NULL”.”OUTLN”.”Dept”;In this SQL statement, ABC.test_VT is Virtual table name“ORCL_11G_WIN”.”NULL”.”OUTLN”.”Dept”;- Remote location for creating Virtual table

When a remote source is added, you can see all the existing tables under that data source in HANA Studio. Next is to create virtual table mapping to data in the remote data sources in SAP HANA Studio. This can be done using GUI option.To add a table as a virtual table, you need to navigate to remote data source → Schema name → Table name → Right-click and Add as Virtual TableBelow shows how you can add a table as a Virtual Table using HANA Studio.

Note that while modifying or creating the property configuration file, only the property which is different from default value needs to be set. The mistake in property configuration file may result in incorrect action or result of data source.

When you create a new remote data source, SAP HANA Smart data access parse the respective property configuration file. With the use of config file- features, function mappings, data type mappings, and other properties will be linked together with the data source. This decides the communication between the SAP HANA and the data source.You can see part of the content of property_orcl.ini shown below −

You can check the following example to create a new remote source −CREATE REMOTE SOURCE TEST_11g ADAPTER “odbc” CONFIGURATION FILE ‘property_orcl.ini’ CONFIGURATION ‘DSN=oral11g_lnx’ WITH CREDENTIAL TYPE ‘PASSWORD’ USING ‘user=username;password=password′;In above SQL statement, can be one of −  ASEODBC, IQODBC,TDODBC, HIVEODBC,ODBC. Obviously, ASEODBC is for Sybase ASE as data source, IQODBC is for Sybase IQ, TDODBC is for Teradata Database, HIVEODBC is for Hadoop.

In SAP HANA SPS07, following data sources are supported under Smart data access −Sybase ASESAP Sybase IQTeradata 13.0 or higherApache Hadoop 2.3MSSQL 11Oracle 12cWhen you click on the Adapter name while creating a new remote data source, you can see a list of all supported databases.You can also see in the above snapshot that all databases use the ODBC connection for a remote data sources.

The remote system access communication is based on ODBC connection, and ODBC drivers for remote data sources − ASEODBC, IQODBC, and TDODBC. To create a remote data source, Right-click on Remote Sources → New Remote Source

In SAP HANA database, you have different system schema. _SYS_BIC schema in SAP HANA database is used to store column views of all the activated objects in HANA repository.  When an object is created and activated (HANA Modeling views, Stored Procedures), run time objects are saved under _SYS_BIC/Column views in database.These column views are used by front-end tools like BusinessObjects to get the data in a query.