Navigating the Database Landscape: Joins Unveiled in SAP - A Practical Guide
Welcome back everyone, We have started to discuss about joins in the last blog, So let’s continue it. In our last blog, we were using for all entries, and for using for all entries, We had seen that we had to write multiple select queries to fetch data from multiple tables. Now we will see how we can get data from multiple tables using joins. Q. Whether we should use for all entries or we should use joins to get data from multiple tables ? Ans :- When we are working on traditional database systems (like Oracle, DB2, Sybase ), we should use for all entries in i.e. We will write individual queries to fetch data from multiple tables. But for HANA database we should prefer Joins. Q. Why we should not use Joins in traditional databases ? Ans :- It is because when we use joins, it fetches data from multiple tables and because of that load on the traditional database system is high and therefore, we should prefer for all entries in but HANA is a very powerful database and we can use