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
- :
- SQLServerLogin
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
‎Dec 05, 2007
02:51 PM
SQLServerLogin
I am trying to use for the first time the capability in IS 2008 to create a database from a script. When I run the script in the SQL Server 2005 tools or using SQLCMD all works fine so I now the script is good.
The documentation is very poor around the architecuture process flow on what and how to do this. I am using the SQLServerLogin form, and I have a SQLConnection and SQLScript associated with it ( the same script I tested).
I get no errors or messages back from the system and nothing ever gets created. Any good samples or better documentation out there?
Gary
The documentation is very poor around the architecuture process flow on what and how to do this. I am using the SQLServerLogin form, and I have a SQLConnection and SQLScript associated with it ( the same script I tested).
I get no errors or messages back from the system and nothing ever gets created. Any good samples or better documentation out there?
Gary
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 06, 2007
01:37 AM
All you need to do is to add connection(s) and your script(s) in the SQL Scripts view. InstallShield automatically displays the built-in SQL Login dialog at runtime. Once you provide valid login information on the dialog, InstallShield will execute your scripts during installation. I recommend that you test it by creating a new project with only adding a connection and a script.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 06, 2007
06:30 PM
Looks you are correct. The problem is in the script. The export wizard to create the script has a few problems. Only way to tell or test is by importing the script into SQL Server and ran the script from there. I was then able to get all the errors.
Thanks!
Thanks!