Run an analysis upon a existing RUN scan ID with "Delta" Mode for ISPAC files analysis

[fpatou]

Hello

Imagine that a ispac file (SSIS project) is modified it would be great to update the analysis of this project for an existing RUN. (using ISPAC file name and Timestamp)

The use case of this would be to run an analysis if the program have failed for any reason
Manage the change of an ispac file after a change in dtsx after a development process.

Regards

[keif888]

Is the scenario you are chasing where you have many ISPack's that have been analysed previously in a single execution (single RunKey value), and you want to update just one of those ISPack's?

Maybe a better enhancement would be the ability to merge multiple RunScan entries into a new one?
In this case, each ISPack is scanned separately (and gets it's own RunKey value), and then you can choose which RunKey's to combine together for view/reporting. This would generate an entirely new RunKey, and associated metadata, which is the combination of all the selected RunKey's.
That way you can scan to a new RunScan record an updated ISPack, and then merge the appropriate set.

[fpatou]

hello Thank you for your answer...on our side(a colleague "Tgauchet" and I ) we are working to industrialize the analyse through a SSIS package to scan a directory with updated ispac file.(first run take all the file)

We are thinking of managing a view giving the last run for each ispac file aggregating all the run.

Our first objective is to be able to produce a extraction dedicated to our development team to find table dependencies upon our 1200 packages/100 ispac.

In the next days the analyser exe file will be deploy on our dev SSIS server to be trigger throughout the ssis package.

We will let you know if this do the tricks to produce this tool dependencies :-)

Thank you for your help !