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