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
- :
- sql script takes a really long time
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
‎Aug 28, 2009
12:04 PM
sql script takes a really long time
I have this huge script about 87000 lines and it takes like 25 seconds to run in the sql management studio but when the installer runs the same scripts it takes like 40 minutes to finish :confused:
any help?
any help?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 28, 2009
12:37 PM
Would it be possible for you to send me the SQL script at hyamanishi@acresso.com so that I can take a look?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 28, 2009
06:17 PM
just emailed the script to you
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 02, 2009
05:41 PM
Thank you for providing your SQL script. However, I was not able to run it successfully because there are several scripting errors. Would it be possible for you to send me a working sample SQL script?
In the meanwhile, you may want to try changing InstallShield to use the Microsoft SQL Server Native Client OLE DB Provider, and see if it makes any differences. By default, InstallShield uses the Microsoft SQL Server OLE DB Provider to connect and run SQL scripts against Microsoft SQL Servers. You need to follow the steps below in order to make the change:
[LIST=1]
Go to the ISSQLDBMetaData table in the Direct Editor.
Find the "MSSQLServer" row.
Change the AdoDriverName column from "sqlolddb" to "sqlncli".
Change the DsnODBCName column from "{SQL Server}" to "{SQL Native Client}"
Rebuild and run your setup.
Regards.
In the meanwhile, you may want to try changing InstallShield to use the Microsoft SQL Server Native Client OLE DB Provider, and see if it makes any differences. By default, InstallShield uses the Microsoft SQL Server OLE DB Provider to connect and run SQL scripts against Microsoft SQL Servers. You need to follow the steps below in order to make the change:
[LIST=1]
Regards.