Killing the “SQL Server is a Memory Hog” Myth
At least once a week I read or hear the familiar refrain, “SQL Server is a memory hog,” or “SQL Server uses all the memory.”
At least once a week I read or hear the familiar refrain, “SQL Server is a memory hog,” or “SQL Server uses all the memory.”
After upgrading to SQL Server 2016 is complete you will need to perform a series of tasks to verify that database is ready to be handed over to the end users for further testing. This post will provide you a checklist of items to review after the upgrade is complete.
Let’s look at the steps involved in upgrading to SQL Server 2016.
Trust me when I tell you that the extra legwork now will save you headaches later. Here is my checklist of items for upgrading to SQL Server 2016 that you must review before any data is migrated.
There are new performance features, new security features, and new scalability features in SQL Server 2016 that make it worth the time and effort to upgrade.
At some point in my career, I had been bitten enough times by linked servers failing to connect that I built a way to automate the checking of the linked server connections.