Sage 100

Installation of program mods on 2014 SU4 PREMIUM before data was migrated took a normal minute or two each. I have mod install instructions which require the mods be reinstalled after migration but before data conversion. The installations of the same mods on the same 2014 SQL version with data migrated are taking 15x longer to complete that the same install did before the data was migrated. This was an upgrade from MAS200 4.40 so I upgraded that to 2014 ADV SU4 first and that upgrade had the same install process / files and both the installs before data migration and after were normal times. There is no changes to the environment other than this, dedicated & separate server for test upgrade, has been rebooted several times. This suggests there is a correlation between installing mods to a Premium version with data is related to the much longer install times. Has anyone else see this and more to the point why would this be the case?

Which mods specifically are involved in this case?

ACS MultiBin + 4 ISM mods that are old Extended Solutions. I am also seeing that the data conversion that is now running is super slow, it may take days to convert. Could it be related to SQL Server is installed on same server as Sage 100 and now that SQL has data its somehow a resource issue where without the data it was not?

It sounds like the installer for the mods is doing some kind of pre data conversion routine perhaps and it's slow for the same reason the actual data conversion is slow. Not sure in this case. Is the pvx data very large (approx how many MBs) - are there segmented files with the .001 extensions? If it's not terribly large, check your Sy_SqlOptimize.m4t with DFDM - see if it's missing entries compared to your Sy_SqlOptimize.m4t

To clarify, if records for custom or standard tables are missing from Sy_SqlOptimize (which is a pvx data file you can check out with DFDM) then slow performance is the usual result.