During recent Comprehensive Database Performance Health Check, one of my customer asked if I can also help them to check their readiness of In-Memory OLTP Migration as well as the help them build a checklist which can help them with In-Memory OLTP Migration.
I consider myself as a SQL Server Performance Tuning Expert and I believe if there is any troubleshooting issue with SQL Server performance, I am sure I would have seen them in the past. I like to engage myself in the performance tuning issues which are very difficult to solve. In the normal case, I would not like to divert myself to different task while working on a performance problem. However, in this case, generating a checklist was a very simple task, hence, I immediately helped them to generate one.
In this blog post, we will see how quickly we can generate an In-Memory OLTP Migration Checklist.
First, go to SQL Server Management Studio and go to Object Explorer and right click over it. Right after that following the image below and go to Tasks and select “Generate In-Memory OLTP Migration Checklists”
It will bring you to the introduction screen. Click Next on the same.
In the next screen, you can specify the location where you want to save your files. Additionally, here you have an option to either select specific table and stored procedure or just go ahead with all the objects in the database.
Once you click next it will bring you to the final Summary screen. Click on the Finish over here.
Next, you will see a screen which will show you the results of the generating migration checklist. There is a good chance that for every single object you will see the result as a “Passed“, however, please note that this result is only informing you that they have created the checklist. To see if your object has passed the In-Memory OLTP Migration Checklist or not, you will have to go to the folder which you have specified earlier.
Once you go to the folder you will find your database name and under the name of the database, you will see folders for Tables and Stored Procedure.
Click on any of the HTML files and you can see that the actual result of the migration test.
If you see Validation Result as a successful, you do not have to worry about anything but if your validation has failed, you will see the status as Failed: More Information. Over here you can click on the file and it will open Microsoft Documentation for further help.
Reference: Pinal Dave (https://blog.SQLAuthority.com)
Pinal, thanks. It would seem helpful if you could indicate for readers which versions of both SSMS and SQL Server support this.
Good Point. I have always used latest and greatest available :)
Fair enough, but of course not everyone can. Are you affirming that you would or would not be updating this post to clarify things. It’s just not clear from your answer.
I appreciate that you’re very busy and do post so much already. Just want to set expectations for other readers who may be interested to know.
SQL Server changes so much nowadays. It is impossible to keep count on when various features were introduced. I personally have no idea when this feature was added. However, it works in the latest version of SQL Server and the latest SSMS when the blog post was written.
I have stopped providing information about version as it had created a lot of confusion for people and also there are many different varieties. Additionally, some features of SSMS works with some earlier version of SQL Server as well. It is an impossible task, in all reality.
To answer your question, if you install the latest SQL Server and SSMS on the date when the blog was written, you will see this feature. I will be not updating the blog post with version information.
As per my knowledge, this feature is available from SQL Server 2016. So, if anybody installs SQL Server 2016, they can be able to use the feature in SSMS.