Hello and welcome to the SAP HANA Academy.
You are watching the video tutorial series: What's New for SAP HANA 2.0 SPS 01.
The topic of this video tutorial is Installation and Update.
Hi, I am Denys van Kempen.
HANA 2.0 SPS 01 introduces the feature that was expected by most for the initial HANA 2.0 release SPS 0:
multitenancy as default operation mode.
For those of you that are a bit dusty on the topic and need a reminder,
here we have the different deployment types of SAP HANA -
an illustration from the Installation and Update Guide.
In HANA 1.0, typically, every SAP application had a dedicated HANA system, running on dedicated hardware.
With restrictions, alternative deployment types for production were available.
With the acronyms MCOD and MCOS: multiple components one system, and one database
respectively,
which allows you to either run two applications in a single database
or run two HANA systems on the same hardware.
MCOD has security implications, obviously, and MCOS requires a lot more compute power,
unless you are willing to accept a considerable drop in performance.
All-in-all far from ideal, hence the restrictions.
So, as of SPS 9, HANA 1, November 2014, a win-win solution was provided that was both
secure and made good uses of compute resources: multitenant database containers, MDC in short.
Here, two or more applications are hosted by a single system yet shielded from the outside
world in an isolated database container.
This has been around for almost 3 years and now with HANA 2 SPS 1, the dedicated deployment
mode on the left is no longer available and MDC is the default, standard operation mode.
In other words, as of SPS 1, all HANA systems are multitenant.
Here we have the SAP HANA lifecycle management tool, the HANA installer, if you will.
Previously, there was this screen - step 4b - where you defined system properties.
Select deployment type This has been removed.
So, when you install an SPS 1 system it will automatically be multi-tenant.
The default or initial tenant database name will be the same as the system identifier.
When you upgrade a HANA 1 or HANA 2 SPS 0 single-container system, you will get this screen.
You need to specify the credentials for the original database and provide a password for
the SYSTEMDB system database user.
What happens, in fact, is that the original database will now be flagged as a tenant and
a system database is added.
The original database will stay intact, same ports are used, so all of your applications
and clients can connect as before.
In the summary screen, we get an alert pointing to note 24 23 367.
Multitenant database containers will become the standard and only operation mode
and this note explains what you need to know.
You will no longer be able to operate a single-container system;
explains the major differences; mentions that a system database is added but
the database size will stay roughly the same and performance is not impacted.
The systemdb indeed is very small.
It just a nameserver process hosting a rowstore database.
Mentions that the upgrade is quick and no user data is changed or migrated.
Again, we only add a systemdb.
The original database stays the same as it was.
Here as well, the tenant database name will be the SID of the single-container system.
Existing applications do not need to be changed.
What do you need to be aware of?
Well, system operations might change a bit.
You now have to make a backup of both the systemdb and any tenant database.
For example, documented here in note 24 36 966 -
you need to re-register your single-container HANA database in studio as it is a tenant database now.
Just a small example of some operations steps you might need to change.
The option to convert a single container system to a multitenant system has been removed from
the resident lifecyle manager tool.
This is no longer needed.
Here we see version SPS 0 and SPS 1 side-by-side.
All of this is documented, of course.
There is a section about updating a single-container system.
With an illustration of the upgrade process and the impact on configuration, security,
and backup and recovery.
Also, the chapter Overview of SAP HANA Tenant Databases has been moved
from the Administration Guide to the Server Installation and Update Guide.
For clarity and this explains the concepts a bit.
Of course, there is a playlist as well on the topic on the SAP HANA Academy:
Multitenant Database Containers including an overview video for the concepts.
Apart from this, the installation guide for SPS 01 is pretty much the same as for SPS 00,
which, in turn, was pretty much the same as for HANA 1.0 SPS 12.
In other words, installing SAP HANA server, client, or other components is nearly identical
for the last couple of releases, not much change here at all.
It is the same code base after all, HANA 1.0 and HANA 2.0.
So, as a quick recap, what's changed for installation and update for SAP HANA 2.0 SPS 01,
Well, for those that were already working in the multitenant database container mode there isn't really any change.
but for those who are still in the single-container environment
there is some reading to do and you probably will have to change some of your operational processes
OK. So much for Installation and Update, What's New for SAP HANA 2.0 SPS 01.
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 we also have a page on Facebook and Google+.
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 his video.
Thank you for watching.
For more infomation >> Eczema rash | 8 Root Causes Of Eczema Doctors Never Treat - skin rashes - Duration: 4:06. 
Không có nhận xét nào:
Đăng nhận xét