Introducing HANA sql script
The purpose of this guide is to simplify SAP HANA sql
script. It differs from all the sql courses available. The sql language is
looked at in detail, starting with a comprehensive look at the notation and
syntactic elements and then progressing to cover the individual statements.
Other courses may jump straight into the SELECT statement, for example, the
following course spends almost all of the course introduction covering the
installation of the database and only 42 seconds on SQL statement Fundamentals.
This pattern is repeated across blogs, online tutorials and
MOOCs. No time is spent on teaching the notation and general syntax. Everyone
jumps straight into the SELECT statement. Once more complex syntactic elements
are reached, the student may get lost as the general principles have not been
mastered yet and learning stops.
We believe that the first step in mastering sql is
understanding the notation used in SAP’s documentation – a ‘Teach a man to
fish’ approach. Once the notation is mastered, getting to grips with the rest
of the language is significantly easier. You will be able to craft complex and
efficient queries more effectively.
Why SAP HANA sql script?
We get this question often. So why did we choose to write a
guide on SAP HANA sql. The reason is that SAP is the leading ERP provider with
more than 12 million users, 121 000 installations and 41 200 customers.
There is an additional imperative for customers to move to SAP HANA. At the end
of 2025, SAP is sun-setting support for legacy software, such as SAP ERP and
BW. Customers will have to upgrade their database to HANA, and upgrade their
software to S/4HANA. A large install base, demand for skills and our enthusiasm
for the SAP platform in general, choosing to create a course on SAP SQL script
is a no-brainer.
Should you require a SAP system to practice or try this out, follow the steps on 'How to activate your own SAP HANA system on the SAP Cloud Platform'
<< Return to table of contents
Lesson 2: The sql script language>>>
No comments:
Post a Comment