PDA

View Full Version : SetupBuilder MsSql Installer



NewsArchive
07-30-2018, 08:20 AM
Hi,
I have a Solution that runs over MsSql, I have a SB installer thet works
ok but the user needs to have a MsSql Express database installed.
I dont want to add the MsSql 2008 core inside my installer because it is
so big and this installer is used to upgrade the solution too.
Im thinking of doing a second installer just to install MsSql Express
2008 and restore de example database, and have the possibility of call
this second installer from the main if the database are not instlled.
How is the best way of do this?
Any example of SB installing MsSql and restoring a database?
Thanks

--
*Alberto Michelis*
ARMi software solutions www.armisoftware.com <http://www.armisoftware.com>

NewsArchive
07-30-2018, 08:27 AM
Hi Alberto,

> Any example of SB installing MsSql and restoring a database?

Have you posted on the Lindersoft forums
(http://www.lindersoft.com/forums) or on the setupbuilder newsgroup on
this nntp server? The newsgroup has been around for a long time and I
recall posts about exactly this in the not so distant past. The
newsgroup is posted as a read-only group on the forums so it's easy to
search it as well as the entire forums :)

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC

NewsArchive
07-30-2018, 08:27 AM
Hi Alberto

>How is the best way of do this?

I faced this same issue many times in the past.
The absolute best way is to go on-site and install the MSSQL server.
or you connect with soemthing like TeamViewer and run the install.
Next best, is as you detail, a separate SB based MSSQL installer, and then the restore
of your database.

You then run the restore of your DB using a small batch that calls SQLCMD . Again, do
this from a small SB installer, or at the very first time your program runs.

One issue where my separate installer failed, was when a client already had an
instance of MSSQL installed by some accounting package they were using. And no, they
would not allow any other uses of that Instance of MSSQL. So I then started my own
naming convention for any MSSQL Instance I would install and use. Anything but the
default instance name of "SQLExpress". That solved some issues.

JohnG

NewsArchive
07-30-2018, 08:29 AM
Discuss with Friedrich. I asked him some years ago and it was basically too
hard. The MSSQL Express installer is much better these days, but I agree with
John, if you can go onsite, install it yourself.

Geoff B

< Never waste the reader's time. >

NewsArchive
07-30-2018, 08:29 AM
Thanks all,
I need not to install myself.
I want it to be automatic for the user, the idea is that it can be
downloaded from a web, install and use.
Regards

*Alberto Michelis*
ARMi software solutions www.armisoftware.com <http://www.armisoftware.com>

NewsArchive
07-30-2018, 08:30 AM
I did this several years ago. Quite a chore. I've been wondering recently if
it couldn't be made an option (script?) in SB.

Greg Fasolt
GFasolt.com