Hi all,
I'm looking to migrate all existing maps from an old instance of SolarWinds to a new one. Requirements specify that I can't migrate the database, so I've had to do a piecemeal migration using a donor box and scripts etc.
Now, the last step is migrating the maps. Research revealed that all the information for the Maps resides within the dbo.MapStudioFiles table in the database. If I simply export this table and then import it to the new database, since they're both running the same version now I've upgraded the donor box to the same version as then new live instance, will all the functionality and click throughs work? My concern is that as the NodeID fields will be different, since it's a automumber primary key for the dbo.Nodes table and I've imported the old nodes, and if the maps refer to this (which they likely do) then whilst I'll have the layout, they will be broken from a functionality perspective.
Unless Atlas is clever enough to look things up beyond NodeID, or can do some fancy repairs behind the scenes when the maps are loaded....