Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation.
To learn more about these changes please visit the announcement which can be found
I have an ssis package which retrains two mining structures (1 structure has 1 model, the other structure has 3 models). The retraining tasks have always been fast, however we recently made some schema changes and now the retraining task of the mining structure
with three models is very slow . I've let it run for several hours and then I have to stop the package, restart the SSIS service and then try again. How can I troubleshoot what exactly SSIS/SSAS is getting stuck on? When I look at SSMS
when the package is retraining the model, the activity monitor is flat line at 25% CPU usage and the "recent expensive queries" list shows the sql used in the view used as the OLE DB source to feed the model training task. However that view takes
only 7 seconds in SSMS to do a select * from so i dont see why it would be stuck on it.
I've opened the tasks in SSIS and nothing appears to be in error (like the meta data warnings), and I am amble to browse and process the mining structure/models in SSMS very quickly.
I resolved this myself. The schema change made the view which was used in the training task to do a full table scan, instead of using the index, and as a result the ssis training task went very very slow pulling the data into SSIS.
Ditandai sebagai Jawaban olehZackBostonMA01 Agustus 2012 19:13