1

Wix installer custom action runs a SQL script to transfer data from old database to new. But the script will time out on larger databases. It doesn't timeout when run manually on Management Studio. Is there a way to lengthen the timeout to 20 minutes?

If not, my backup plan is to break up the script into smaller chunks.

Brian
  • 307
  • 2
  • 15
  • 1
    Can you do this from within your application (if any), instead of inside the setup? – Stein Åsmul Dec 02 '19 at 20:40
  • Yes we can, but we can also just run the script in management studios. We are trying to eliminate work. This did give me an idea, create a separate application that runs inside the setup. – Brian Dec 02 '19 at 20:47
  • 1
    Custom actions are very difficult for a number of reasons. [Here is a short summary](https://stackoverflow.com/a/56507479/129130), and would you know, [here is a whole rant](https://stackoverflow.com/a/46179779/129130). Essentially: try to put it in the application, you will save yourself some serious blues and you will be in a familiar context for debugging? – Stein Åsmul Dec 02 '19 at 21:40
  • Feel free to add your own answer if you like? So others can see how you solved the problem. – Stein Åsmul Dec 04 '19 at 17:09
  • Thanks Stein, I haven't solved it yet, but I'm close to getting it to work through an application. – Brian Dec 04 '19 at 18:32
  • Update, putting the SQL into an application solved the issue. – Brian Jan 15 '20 at 22:58
  • Great, that always helps to get deployment simpler and application launch and configuration more "interactive". Good luck with all the testing. "*The last meter is long*". Gets tiresome. – Stein Åsmul Jan 15 '20 at 23:57

0 Answers0