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: SQL Schema Not Being Respected on Update
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
‎Sep 23, 2014
10:24 AM
SQL Schema Not Being Respected on Update
My ISSchema table in my target MSSQL database has the following entries:
0005.03053.0001
0005.03053.0002
0005.03053.0004
When I am running an update to the installation, the installer is running a script with a schema value of 0005.03045.0001, which I don't believe it should be, based on the documentation. I have confirmed that the installer is running with the proper login and permissions to run the scripts, so I do not understand why this script is being run. Can anyone point me in the direction of understanding?
Thanks,
Chris
0005.03053.0001
0005.03053.0002
0005.03053.0004
When I am running an update to the installation, the installer is running a script with a schema value of 0005.03045.0001, which I don't believe it should be, based on the documentation. I have confirmed that the installer is running with the proper login and permissions to run the scripts, so I do not understand why this script is being run. Can anyone point me in the direction of understanding?
Thanks,
Chris
- Tags:
- schema version
- sql
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 06, 2014
10:06 PM
It's not reproducible on my end. I added the same ISSchema records to my target database as explained in your post above, and a script with a schema value of 0005.03045.0001 wasn't executed against that database. A verbose log may help you troubleshoot to find out why your script runs. The KB article Q106551 explains how to create the log.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 07, 2014
04:45 PM
hidenori wrote:
It's not reproducible on my end. I added the same ISSchema records to my target database as explained in your post above, and a script with a schema value of 0005.03045.0001 wasn't executed against that database. A verbose log may help you troubleshoot to find out why your script runs. The KB article Q106551 explains how to create the log.
Thanks for the tip, I will let you know what I find.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 17, 2014
03:59 PM
I tried the logging as you suggested, and no log file was created. Then I found this page (http://helpnet.installshield.com/installshield18helplib/IHelpSetup_EXECmdLine.htm), which indicates that the logging doesn't work for InstallScript projects that aren't MSI. Do you know of some other way that I can debug this issue?
Thanks,
Chris
Thanks,
Chris