Re: [WiX-users] SQL Script limit?

[Albert v. P. <Al...@in...>]

Hi,
=20
I am handling this in my application; when the app is executed for the
first time (it checks this) then the database is created by the
application. This way you have more control over your database creation
process.
It also runs much faster indeed and when the application is already
installed you can use some logic of your own to determine if the
database needs to be updated or not.
=20
I think installing something that takes more than one hour is something
i would consider as bad; As a standpoint of a developer as well as a
standpoint of a system administrator.
=20
But i can understand that it is sometimes not possible to install your
database at first run. In this case i would recommend using a CA. In
this case you have lowlevel access to the database which means speed.
Inside MSI installer it is hard to tell what the problem is, i think
data is copied around which means lots and lots of memory is wasted, add
to that the memory usage of SQLServer (assuming the SQL Server is
running on the same machine as you are installing) and you have a
blueprint for disaster whith such a SQL script (which will cause a huge
transaction log in SQL memory i supose).
=20
Regards,
=20
Albert van Peppen
=20


________________________________

Van: wix...@li...
[mailto:wix...@li...] Namens Rob Mensching
Verzonden: woensdag 24 januari 2007 16:15
Aan: Ian Couper
CC: wix...@li...
Onderwerp: Re: [WiX-users] SQL Script limit?



Wow, you have a SQL Script that takes an hour to run?  I've never seen
anything that complicated.  Again, as I noted below, due to the way data
is passed around inside the Windows Installer, your script may be copied
around several times.  Also, the WiX toolset is doing a bit of
processing to break your script down to pass it around inside the
Windows Installer.  It is entirely possible that is causing the overhead
you're seeing.

=20

Just a general question, "What is in a 50 MB SQL Script that you need to
execute at install time?"  A one hour wait during installation is not a
great user experience.  I'm just trying to understand what the WiX
toolset could do to help.

=20

From: Ian Couper [mailto:ic...@op...]=20
Sent: Wednesday, January 24, 2007 6:25 AM
To: Rob Mensching
Cc: wix...@li...
Subject: RE: [WiX-users] SQL Script limit?

=20

I just let the script run overnight and it finally did something. It
ended up failing on some line from the script, but aside from that the
script took almost 4 hours to run to that point, which wasn't even to
completion. This script normally takes about 20 min to 1 hour at the
most to run, so there is either something wrong with how I am handling
it, or WiX can't handle the size of script I am trying to run.

=20

________________________________

From: Rob Mensching [mailto:Rob...@mi...]=20
Sent: Tuesday, January 23, 2007 11:55 AM
To: Ian Couper; wix...@li...
Subject: RE: [WiX-users] SQL Script limit?

=20

With the way that MSI works, you'll probably end up pushing the same 50
MB of strings around 3 or 4 times.  That could take time.  Also, if you
don't have the latest WiX v2 code base, you could be hitting some old
bugs in the SQL processing.

=20

After that, you could try debugging through the code and seeing what is
taking the longest.  Maybe there is some perf we can improve, but I've
never heard anyone complain about this before.

=20

From: wix...@li...
[mailto:wix...@li...] On Behalf Of Ian Couper
Sent: Tuesday, January 23, 2007 8:25 AM
To: wix...@li...
Subject: [WiX-users] SQL Script limit?

=20

I have a large SQL script (30 to 50MBs) that I am trying to run from the
MSI using SQLScript. I have been able to run smaller scripts easily, but
this large one is not running at all and the MSI hangs. Is this a known
issue with Wix 2.0? Is there a way to overcome this issue?

=20

Thanks.