Our DBAs did see this KB as well. It didn't apply in our case because we were already beyond the CU level mentioned and the APM_ApplicationTemplate Table only had 850 records in it, less than the > 4000 mentioned in the article.
For testing purposes, we did set up an environment with absolute latest SQL 2016 SP2 CU 10, loaded the Orion environment from before the upgrade, and still had the corruption.
One other suggestion from the team is that if you still have this corruption present on your test environment run the following:
exec sp_tableoption 'dbo.APM_ExternalSetting', 'large value types out of row', '1'
exec sp_tableoption 'dbo.APM_ApplicationTemplate', 'large value types out of row', '1'
exec sp_tableoption 'dbo.APM_ComponentDefinition', 'large value types out of row', '1'
Thank you for the update! We have blown away that environment, unfortunately.
One suggestion I have is to add in a DBCC CHECKTable against the whole database as part of an upgrade process to identify potential issues before a sign off that the upgrade was successful. We will be adding this to our upgrades moving forward. Not sure of the ramifications of adding it to the wizard (It can take some time depending on the DB size) but thought I'd make the suggestion.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.