hi all,
we currently use an installshield conflict solver SQL database which all our packages get imported to.
This project has been going a long time now and will continue for another year at least.
At present there are 600 packages in the db, so any time we import a package its takes a long time to complete which is making life painful. I am just wondering does anyone have a smarter implementation design out there?
Is the above design the typical scenario or are we missing something?
any ideas welcome and appreciated.
0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity