I know I promised a features post to MEMCM 2006 as my next post but, the truth is, I just don’t feel like it today. What we will look at is upgrading your site database from SQL Server 2017 to SQL Server 2019. This is a pretty painless process, being almost entirely wizard driven. That doesn’t mean to say it isn’t without risk. So, standard disclaimer here. Back up your site, back up your SQL database, take a fucking snapshot of your server. Do all three. You’ll thank me if something goes catastrophically wrong. Oh and back up those custom SSRS reports you have too. You can never be too careful.
First thing to do is to stop the SMS Executive service on your server. You can do this a number of ways, but I prefer to do it via the console to validate the other services have stopped. Go to the Monitoring workspace, System Status node and Component status. Click Start in the ribbon and select Configuration Manager Service Manager.
Expand you site and select Components. Scroll down to the SMS EXECUTIVE service and right click. Now you’ll notice all the fun stuff (Start, Stop, Pause) is greyed out. That’s because, in an effort to save loading time, the services state isn’t enumerated upon opening. Instead, right click and select Query. This will take a couple of minutes to query the service as to its state and will return the ultimate state of SMS Executive. Hopefully, that’s in a running state. Otherwise, you might want to skip this blog post and open a support ticket with Microsoft.
Now that we’ve queried the state of SMS Executive, we’ll need to stop the service. Right click again and select Stop. This will cascade down to the other services and stop them as well. I gave it about five minutes in my lab, but YMMV in production. You’re welcome to query the other services to validate they’ve stopp, but be warned this is very time consuming.
SMS Executive showing stopped. Duh.
Now mount your SQL Server 2019 ISO and run Setup.exe. It will launch the SQL Server Installation Center. Click on Installation, because who needs planning?? Select Upgrade from a previous version of SQL Server.
The installation wizard will then launch. I’m not going to walk you through every single selection for the purposes of this blog post. If you need to know if you need to do a full text upgrade, might I suggest Google for the quickest result. My collegue would suggest Bing, but there’s just something wrong with him.
Select your instance to upgrade. If you’re running a standalone SQL Server for the express intent of MEMCM, then it should be selected for you. If you’re hosting this on a massive, catch-all SQL Server, please stop. Your DBA is going to be fucking pissed at you.
All of the appropriate features will be selected. This is what my lab looks like. When I did our production SQL Server 2012 to SQL Server 2019 upgrade things looked a whole lot different.
Now, the next few screens will take you through Instance, Server and Full-text Upgrade Configurations. I’m omitting these simply because I really have nothing to say about them and I’m not one for including screenshots for the hell of it.
Finally. Ready to upgrade. Click that Upgrade button, go make a cup of coffee and turn on the news. This takes a little while. Even in my tiny lab environment it took a good twenty minutes to complete.
If everything goes according to plan, you should see this screen upon completion. It’ll usually be accompanied with a message to reboot your system. Reboot that sucker at your earliest convenience and bask in the glory of being on the latest, greatest version of SQL Server!
Once completed you will probably want to upgrade SQL Server Management Studio as well as SSRS (although, I didn’t find that necessary going from 2017 to 2019). This is a quick and relatively painless upgrade path to SQL Server 2019. If you’re going from any other version, the upgrade can be a little more involved, as referenced in my mention of the 2012 upgrade I did a few weeks back. Feel free to drop any comments below and remember, Configure This!