Hello and welcome to the SAP HANA Academy.
The topic of this video tutorial series is SAP HANA Cockpit and in this video we will
discuss what’s new or changed for this release of SAP HANA database explorer.
This video has been recorded on release SAP HANA cockpit 2.0 SP 08 from October 2018.
For earlier or later releases, please check the playlist on the SAP HANA Academy.
Hi, I am Denys van Kempen.
We can access the Database Explorer and the SQL Console from the SAP HANA Cockpit Landscape
Overview page.
There are two tiles: Browse Database Objects and Execute SQL but they open the same app.
Another way to access is to select the Open SQL Console link from the header of the System
Overview page for a particular database.
This will open a new SQL Console tab with a connection to as the current user to the
current database.
SQL Console and Database Explorer; it is a single application —you can bookmark it,
of course, if you want to access it from your browser toolbar and not from cockpit— by
now, most of the functionality of SAP HANA Studio from the previous SAP HANA 1.0 release
has been included and more.
We can browse, or explore I guess, I should say, our database objects.
Select the object type to have them listed here below —you can search, if the list
is long.
Context (right-click) menus provide access to the most common actions: export/import
data, generate SQL, open structure or get data.
You get the raw data in rows and columns and you can do instant analysis, pivot tables,
graphs, and so on.
Advanced Search, a Debugger, a Console for Background Activities, and this is related
to the different Run options we have got a here, Run as Background Activites (Ctrl+Shift+F8;
there are keyboard shortcuts for the most common tasks.
Just a quick tour for those less familiar with the SAP HANA Database Explorer, and this
is just for the SQL Console, there is an MDX Console as well, for OLAP multidimensional
type queries.
OK —What’s New?
Some enhancements to the SQL Console.
Of course, the biggest issue with browser-based tools, doesn’t matter if we are writing
an e-mail or writing code in a SQL console is that if, for whatever reason, the web server
does not respond, the browser hangs, etc. and we need to refresh the page or restart
the browser, our data is gone and we have to start all over again.
More and more, this is becoming a thing of the past as current web tools, using Node.js
are perfectly capable of maintain and restoring state.
For the Database Explorer this means that, from the current release onwards, that the
content of your SQL console is now saved when the browser is closed.
The SQL console does a save about 30 seconds after the last keystroke or when you use any
of the Run menu options, always when the console is connected to a database, and when you close
your console.
So, how does this look?
Let’s generate some SQL.
Execute.
Close the console.
Return.
Close the browser.
Let’s create the bookmark first.
Reopen.
No work lost.
Note that I did not use and Ctrl+S save shortcut for this to happen.
You do not need to do anything.
Of course, we do not get our result set back automatically as this would mean that SQL
Console starts to run our queries on our behalve.
Not a good idea.
We have a new icon here on the toolbar, as well, Hide/Show Columns.
If there is some sensitive data in the result set which you wish not to have displayed but
you need to include it in the query, you can now very easily achieve this with this toggle.
Additionally, when you download the data into a CSV file, you can mark whether hidden data
should be included or not.
Minor change: previously, you would double-click a table cell in the data preview to open the
view dialog.
Now, you need to right-click the cell and click View data.
Another new feature is SQLScript Code Coverage
You access Report Code Coverage from the Analyze menu.
We can now very easily see which part of the code executed and which part did not.
Works for SQLScript procedures, functions, and anonymous blocks, which I was using here.
Another enhancement, another new feature, is that we can now view the execution plan
for a SQL statement or procedure.
You can access this with Analyze, Explain Plan.
Operator Name, Operator Details and Properties.
Then we also have, Ctrl+Shift+X, Analyze SQL.
The SQL Analyzer itself is not new, what I wanted to show you is the SQL Performance
Recommendations, which are now also displayed on the Overview page of the Analysis.
In this case, we do not have any, but here you would see the high lights, the summary,
with the details on the Recommendations tab.
Compilation Summary, also new, here we see the statistics used for cost based optimization,
for example.
Table access, tables in use, the timeline, and the Plan Graph, of course, we know from
previous releases.
What’s new in SAP HANA Cockpit 2.0 is documented in the What’s New Guide with a paragraph
about the Database Explorer and you will also find this documented in the dedicated SAP
HANA Database Explorer Guide under Getting Started.
Thanks for watching.
You can find more video tutorials on our YouTube channel.
If you would like to be informed about new video tutorials, please subscribe to our channel.
You can connect with us on LinkedIn or follow us on Twitter, as well for updates, and if
you are watching this video on YouTube, do not hesitate to leave your comments to the
video page and, if you like, give us your vote on this video.
Thank you for watching.