Interview Questions.

Q1: Which non-SAP framework can SAP HANA interface?

Ans: Oracle Enterprise, IBM Informix.

Q2: What are the Views accessible in the Quick send off of Information modeler?

Ans: Navigator, Where-utilized list, Job log, Properties.

Q3: For what Life cycle the executives point of view is utilized?

Ans: We use Life cycle the board point of view to Upgrade/Updates for HANA studio.

Q4: OPD for information replication API is utilized in which replication?

Ans: Data administrations 4.0.

Q5: How could you at any point guarantee that information is predictable in source framework and HANA framework?

Ans: Since any progressions in the source framework are followed in committed logging tables, the replication status for each changed information record is straightforward. A section of logging table is erased after a fruitful commit explanation from HANA information base and this method guarantees the information consistency between a source framework and HANA framework.

Q6: Which area controls the information handling in the HANA DB?

Ans: Transaction Manager controls the information handling in the HANA DB.

Q7: What is the part present in Persistence layer in the HANA DB?

Ans: The part present in Persistence layer in the HANA DB is Page the board and Logger.

Q8: What are the kinds of joins are conceivable in Attribute view?

Ans:

Referential join

Internal join

External join

Q9: What is the job of Persistence Layer?

Ans: It guarantees that the data set is reestablished to the latest committed state after a restart and that exchanges are either totally executed or totally scattered. The diligence layer offers interfaces for composing and understanding information. It additionally contains SAP HANA 's lumberjack that deals with the exchange lo. Log sections can be composed verifiably by the perseverance layer when information is composed through the diligence interface or expressly by utilizing a log interface.

Q:10 What does HANA DB performs During blackout?

Ans: Recovers log between last information savepoint and season of disappointment.

[teaserbox type="4" img="2902" title="Interested in Learning IOT" subtitle="Join myTectra Today!" link_url="http://www.mytectra.com/iot-preparing in-bangalore.html" target="blank"]

Q11: What is the Operating System of IMDB ?

Ans: SUSE Linux Enterprise Server

Q:12 Which is the default viewpoint of IMCE Studio?

Ans: Administrator console

Q:13 Name the releases of SAP HANA Software?

Ans:

Stage release

Endeavor release

Venture broadened version.

HubSpot Video

Q14: What are the advantages of carrying out SAP HANA with SAP ERP?

Ans:

Execution advancement for functional announcing

Handling of huge volumes of information

Arrangement of continuous investigation.

Q15: Do we really want an exceptional driver to get to information inside HANA?

Ans: HANA gives both a 32-bit and 64-cycle ODBC and JDBC drivers. SAP BusinessObjects 4.0, Data Services 4.0 and numerous other SAP based apparatuses have inherent help for these drivers to assist with supporting every one of the elements HANA brings to the table.

Q16: How might we at any point stack information in HANA and how to get to the information put away in HANA?

Ans:

Stacking information: There are a few choices accessible to get information into HANA. SAP gives an ongoing replication server called SLT Replication. With this server you can imitate information from a SAP framework or non-SAP RDMS frameworks into HANA. The information is replicated in its local configuration and will then should be de-standardized on HANA utilizing data sees ( trait sees, scientific perspectives and computation sees). As indicated by the documentation, you can likewise use the Sybase Replication Server for log based replication. What's more, Data Services 4.0 can be utilized to move information into HANA and can refresh information at close to continuous if necessary. Information Services 4.0 can likewise de-standardize the information given its wealth of information changes and give information quality and purging changes that will assist with cleaning the information before it is stacked into HANA.

Access the information: There are multiple ways of getting to the information inside HANA. The best method for getting to information is through SAP BusinessObjects 4.0. There are different instruments inside the BusinessObjects 4.0 stage for getting to HANA information. You can use Web Intelligence, Crystal Reports, Explorer, "Investigation Edition for Microsoft Office", Mobile and Dashboard (Xcelsius). To put it plainly, any device in the stage that upholds ODBC or a Universe can be used to get to information inside HANA. These choices work for SAP BW (fueled by HANA) or for HANA (Standalone). Assuming you have SAP BW controlled by HANA, you can use any of the conventional inquiry apparatuses. For those that like review crude information results, you can use HANA Studios to execute SQL articulations and view the outcomes.

Q17: Why we really want to go for going In-memory?

Ans: One explanation is the quantity of CPU cycles each second is expanding and the expense of processors is diminishing. For dealing with the information in memory, there is five-minute rule which depends on the idea that it costs more to trust that the information will be brought from plate than it expenses to keep information in memory so it relies heavily on how frequently you get the information.

For instance, there is a table and regardless of how enormous it is and this table is moved by a question no less than once like clockwork, it is more affordable (in equipment costs) to keep it in memory than to peruse it from memory and in the event that it is regularly gotten to putting away it in memory is more affordable.

Q:18 What are the upsides of Column based tables and Row-based tables?

Ans:

Benefits of Column based tables:

Estimations are regularly executed on single or a couple of segments as it were.

The table is looked through in light of upsides of a couple of segments.

The table has an enormous number of sections.

The table has an enormous number of lines and columnar tasks are required (total, examine, and so forth.).

High pressure rates can be accomplished in light of the fact that most of the sections contain a couple of unmistakable qualities (contrasted with various lines).

Benefits of Row-based tables:

The application needs to just handle a solitary record at one at once (or potentially updates of single records).

The application normally needs to get to a total record (or line).

The sections contain for the most part unmistakable qualities so the pressure rate would be low.

Neither collections nor quick looking is required.

The table has few lines (e. g. design tables).

Q19: What is Derived Attribute Views?

Ans: In some business cases, it is expected to utilize a similar trait view at least a few times

In such cases, one can determine a trait view utilizing the base view which goes about as reference to the base quality view. The determined characteristic view will be opened in the read-just mode. The main editable field will be its portrayal. The determined quality view will go about as a kind of perspective to its base property view.[teaserbox type="4" img="2901" title="Interested in Learning Devops" subtitle="Join myTectra Today" link_url="http://www.mytectra.com/devops-preparing in-bangalore.html" target="blank"]