Neophyte
ProfessorUpdating DataSources can be nerve racking and can be little risky although I do think LM does attempt to limit data loss from upgrades and will list possible issues in the release notes and support page.
For MSSQL, there is a note at https://www.logicmonitor.com/support/monitoring/applications-databases/microsoft-sql-server#migration-to-latest-logicmodules about instance names might change, which might cause you to lose history. I wasn't able to locate the release notes that cover the update for Microsoft_SQLServer_GlobalPerformance specifically but perhaps LM support can help you locate that.
If you have a LM Sandbox instance setup, you can try using that to test out the upgrade to determine any affects the new DataSource will do.
If you know how to read Groovy code, you can look at the differences between the current DataSource and the new one to see what it changed and perhaps get an idea what might happen.
You can also try installing the new DataSource with a new name so it runs in parallel with the old one. You might need to use a Sandbox instance to import it, rename it, export to JSON, then import into production instance. If you don't have Sandbox instance, perhaps LM support can export the latest version for you and you can edit the JSON file directly.
