The document outlines various technical aspects related to SQL and ABAP, including exception handling, data replication between SAP ECC and SAP HANA, and database procedure management. It emphasizes best practices for SQL queries, such as using ORDER BY clauses and ensuring proper indexing. Additionally, it covers tools like SQL Monitor and ABAP Test Cockpit for performance monitoring and optimization.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
11 views2 pages
HANA ANS
The document outlines various technical aspects related to SQL and ABAP, including exception handling, data replication between SAP ECC and SAP HANA, and database procedure management. It emphasizes best practices for SQL queries, such as using ORDER BY clauses and ensuring proper indexing. Additionally, it covers tools like SQL Monitor and ABAP Test Cockpit for performance monitoring and optimization.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2
1.
SUM CAST CASE
2. It supports exception handling. It supports where-used list. 3. From another database procedure From a Script-based calculation view 4. LOCAL TEMPORARY 5. SQL Monitor Code Inspector ABAP Test Cockpit (transaction: ATC) 6. Missing ORDER BY or SORT after SELECT 7. Increased parallel processing Optimized data partitioning 8. Package ZHA400_00 is listed in table SNHI_DUP_PREWORK. System P81 has SAP HANA as primary database. 9. De-pooling and de-clustering Definition of full-text indexes Storage type for tables 10. Flexible schedule of check runs Enhanced distribution of results 11. All fields in the GROUP BY clause must be separated by commas @ sign 12. To replicate data between SAP ECC and SAP HANA 13. Core Data Services (CDS) data definition Open SQL 14. flights.carrid and planetype _flights.carrid and _flights.planetype 15. _SYS_BIC."ha400.primdb/CA_BOOKINGS_COUNT" _SYS_BIC."ha400.primdb::CA_BOOKINGS_COUNT" 16. Because you can manually re-deploy objects after a failed import. Because you use the technique that is recommended by SAP. 17. The data has NOT yet been transferred to the SQL Monitor database tables. SQL Monitor was activated with a filter that excludes database table Y. SQL Monitor was activated for a specific application server. 18. NEXT_PACKAGE 19. Replace UP TO n ROWS additions. Add explicit client handling Specify the schema for every 20. Deploy a new version of the database procedure when the AMDP is first called. 21. It represents the connection to an ABAP. It provides access to all ABAP repository objects 22. Ensure the WHERE clause contains at least one index field. Use SELECT FOR ALL ENTRIES instead of a nested SELECT statement. 23. Database Procedure Proxy ABAP class with SQL script coding ABAP class with new OpeSQL 24. A BAdI fallback implementation An enhancement spot A BAdI definition 25. _SYS_BIC 26. Capture the SQL profile of an application. 27. Parallel processing 28. ABAP Dictionary views used in the procedure body ABAP Dictionary tables used in the procedure body AMDPs used in the procedure body 29. Double-click on rows Group rows Search in content 30. Map the ADDRESS field to a constant value. Exclude the ADDRESS field from the union. 31. One result set 32. The same number of columns Columns of compatible types 33. Include all fields used in the ON condition in the projection list. 34. Collecting data with SQL Monitor (SQLM) 35. Watchpoints Conditional breakpoints 36. You have to specify the DB schema You have to specify the DB connection explicitly in your 37. The SCORE( ) function is required to ensure the best hits of your search appear on top 38. F3 39. Minimize the amount of transferred data. Minimize the number of database accesses 40. 11 15 13