The following appears to be a very common problem because lots of people have asked about it - but they always get asked for more information and no resolution is ever presented (or at least I can't find one).
We have a SQL script to create one of our databases when the product is initially installed. It is over 65MB. Yes, it runs in SSMS, but when put in an installer it causes the resulting product to hang indefinitely, telling the user "Generating actions to configure databases for install SQL script execution". It uses about 50% of the machine's CPU but accesses no files, nor does it generate any network traffic, nor does it access the SQL Server it is supposed to create the database on. It appears to just spin in place.
I think I saw someone suggest doing something equivalent to splitting the script into 650 separate SQL scripts? That wouldn't be managable.
We are running on Version 9.0. Any recommendations?
Thanks,
Rob
FOLLOW US
Get the latest news in Application Packaging