
One very interesting SAP Advanced SQL Migration tool capability you have probably read about before is the pre-migration complexity assessment and you may wonder how it looks like and how it can help you to take a decision and attack your database migration project. This is exactly what this blog is all about.
When you start thinking about a database migration project there are two important questions arising at the very initial steps:
- How complex is it going to be?
- What is the effort needed to do it?
The pre-migration complexity assessment performed by SAP Advanced SQL Migration will greatly help you answering those questions and will also point out to the parts where you should focus your biggest efforts.
The pre-migration complexity assessment is a section of the conversion log provided by the tool, the typical name of the file is something similar to "SQL-Conversion.Oracle-HANA.YYYYMMMDD.hhmmss.log", it can be found under the scripts folder once the conversion is done and also under the reports folder (it can be obtained as we using the migration tool "analyze" command instead of the "convert" command, check the manuals for more details).
Let’s take a look at the pre-migration complexity assessment output for a very complex case we run into on January 2021 and we will see some other interesting stuff provided by this migration tool as well.
This real case was an Oracle to SAP HANA migration and the head of the summary for this complexity assessment was:
From this info you are getting some interesting numbers to start with:
This sounds like a lot of issues but think about these remarks:
But even more, the complexity assessment also provides deep details about the issues found. This is what is returned under issues with “more impact”:
As you can observe the migration tool is pointing out clearly the features that are not converted automatically into the target database SQL dialect, that is where you will have to do some redesign/rewrite. As pointed out before some of the issues are appearing hundreds of times.
For “less impact” issues we get a similar report as well:
SAP Advanced SQL Migration also provides report at SQL object level with the details about the conversion for the corresponding objects, clearly indicating what is converted automatically with a “Fully converted” indicator or what is not converted by the tool:
SAP Advanced SQL Migration tool complexity assessment is reporting an effort estimate as well, but please don’t take this as final number at all, that will depend a lot on different aspects as the notes are saying, it should be used to get general idea and to do further estimations.
Contact: Advanced_SQL_Migration@sap.com
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
22 | |
12 | |
11 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
5 |