If only there was some way to import it? There is!įirst off, you will need to do this during a maintenance window.
Well, we can always just install the Monitoring Database on the new server defined in the topology, but then we lose all our call history data. We also can’t just Install-CsDatabase -DatabaseType Monitoring -SqlServerFqdn -SqlInstanceName Foo_Lync -update as the old SQL version is not supported on 2019, we need at least SQL 2016 as we can see with a quick Test-CsDatabase This is because the schema versions don’t match and differ quite considerably. You might have noticed during setup, Topology builder won’t let you select yourĮxisting QoE Monitoring database for the 2019 Pool. Okay, So this guide is going to assume that you have Skype4B 2019 installed already and have a Lync 2013 pool to migrate the data from. Always follow the guidance of your DBA or check out more information from the SQL community like fellow MVP and Purplonion Martin Cairney Well with a little bit of SQL fiddling, we can!ĭisclaimer: I’m NOT an SQL guru, as with most things, I know enough to be dangerous. Unfortunately, Topology Builder and the QoE deployment wizard don’t give you any sort of migration utility/steps so you might be forgiven for thinking this isn’t possible.
Or maybe you are looking to take advantage of the new Call Quality Dashboard connector with your legacy data? Why should I do this?Īs part of building your brand new Skype4B 2019 Pool, you might want a single point of truth for all your QoE data, but don’t want to lose your existing Lync 2013 calls. In this guide, we take a look at how to import that existing data into our new Skype for Business 2019 deployment. Skype for Business 2019 is the latest and greatest on-premises UC product from Microsoft, and if you are deploying it in an existing environment as part of your journey to the cloud you may have some legacy call data in your Lync 2013 or Skype for Business 2015 servers.
0 kommentar(er)
