This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: When is Uninstall really Uninstall?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 28, 2008
02:59 PM
When is Uninstall really Uninstall?
InstallShield MSI
I have a SQL Script that deletes my application database from SQL when my app is uninstalled. When doing a Major Upgrade the help states that "the installation typically uninstalls the earlier version from the target machine."
I do not want my Delete Database SQL Script to execute during a Major Upgrade but only if my applications is being removed totally.
Will a Major Upgrade trigger a SQL Script set to "Run Script During Uninstall"?
If so any workarounds?
Thanks
I have a SQL Script that deletes my application database from SQL when my app is uninstalled. When doing a Major Upgrade the help states that "the installation typically uninstalls the earlier version from the target machine."
I do not want my Delete Database SQL Script to execute during a Major Upgrade but only if my applications is being removed totally.
Will a Major Upgrade trigger a SQL Script set to "Run Script During Uninstall"?
If so any workarounds?
Thanks
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 01, 2008
12:12 PM
Yes, the setting 'Run script during uninstall' will run the script during Major Upgrade also. To make the script not run during the Major Upgrade, use the checkbox for 'Script Condition' at the bottom and specify the condition: REMOVE="ALL" And Not UPGRADINGPRODUCTCODE.
From Tech Support
From Tech Support
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 01, 2008
10:17 PM
I would seriously reconsider running a sql script on uninstall. My first reason is you are most likely deleting user data which is not a best practice and two it adds dependencies and fragility to your uninstall.
The only thing worse then a failed install is a failed uninstall...
The only thing worse then a failed install is a failed uninstall...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 04, 2008
09:01 AM
Thanks Christopher,
Very interesting. So best practices would be to leave a database in place even though there would be no use for it? I thought the user would be more interested in regaining disk space if they chose to stop using the application. What if I left the data but removed the stored procedures?
Does anyone else out there have an opinion on this?
Thanks again...
Very interesting. So best practices would be to leave a database in place even though there would be no use for it? I thought the user would be more interested in regaining disk space if they chose to stop using the application. What if I left the data but removed the stored procedures?
Does anyone else out there have an opinion on this?
Thanks again...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 04, 2008
09:31 AM
When you uninstall word, does Microsoft delete all of your .doc, xls, .mdb, .ppt files?
The question is, does the state of the database change after initial installation? If the database is literally nothing more then a bunch of static table data and stored procs/views to access the data and it never, never changes, then fine, go ahead and drop it. But if database changes to include data the user inputted, you should really consider keeping it. They may reinstall the application one day and want to see the data they had inputted.
The question is, does the state of the database change after initial installation? If the database is literally nothing more then a bunch of static table data and stored procs/views to access the data and it never, never changes, then fine, go ahead and drop it. But if database changes to include data the user inputted, you should really consider keeping it. They may reinstall the application one day and want to see the data they had inputted.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 05, 2008
08:29 AM
I see your point. I hadn't thought about the re-install issue.
Thanks again...
Thanks again...