Since SAP released the support for SQL Server 2016 to some products based on SAP Net Weaver – not all products are currently supported, see SAP Note 2201059 – I was preparing my test systems to upgrade to SQL Server 2016.

I took me 2 days to complete all the necessary steps to upgrade the database to SQL Server 2016.

It loads and analyzes performance data collected by Pssdiag.

It can dramatically reduce the amount of time you spend manually analyzing data.

Browse the exam list to find details about skills measured, then click on the links to connect to preparation materials, or schedule an appointment to take the exam with an exam provider.Last week while at SQLBits I attended a session titled SQL Server/Azure Engineering Model given by Conor Cunningham from Microsoft.During the talk, Conor announced that there was an update to the SQL Server 2016 privacy statement.(Note: Microsoft did not create a SQL Server 2016 version.The 2014 version guide should be similar enough for this purpose.) To get a sense for what might be entailed in the upgrade process in your environment, you will want work through an assessment your environment.In the assessment, you will inventory SQL Server instances, document hardware specifications, operating system, software, disk space, what SQL Server functionality is being used, extended stored procedures, custom dlls., what other applications are on the box, and downstream dependencies.After you have an inventory, you will then continue to run Best Practices Analyzer if exists for your current version of SQL Server.I used SPAM to apply the required SAP BASIS in my system, as it made no much sense to use SUM – be careful, if you’re doing a NEW installation on SQL Server 2016, you cannot use SPAM to apply the minimum required SPS for Net Weaver, you have to use SUM – see SAP Note 2201060.After the SPAM update and updating SAP_BASIS, SAP_ABA and SAP_BW packages to SPS 05 each of them (and other dependency packages like SAP_GWFND, SAP_UI and ST-PI), I was ready forthe upgrade, but I had to download the media.Unless you have a personal instance, most real-world SQL Server environments can be complex to upgrade.If you are having a tough time getting planning time, send your manager a copy of the 429 page SQL Server Technical Upgrade Guide to review.My system is a SAP Net Weaver 7.50 (initial shipment, no SPS), ABAP stack,running on SQL Server 2014 SP2, central system with DB and ASCS/DI installed on the same host.Preparation Before going forward I took some time to review the existing SAP documentation about SQL Server 2016.By scanning for best practices, you avoid upgrading bad practices.If bad or questionable practices exist, you should address them before the upgrade, moving the fixes through test and into production.