Prev: Image not getting loaded from My.Resources
Next: Managing delays on dropdown or on tooltopexts
From: John on 19 Mar 2010 10:46
Hi

I have a winform app with sql server backend. How can I create a deployment
package which when run by the end user does the following;

1. Install front end vb winfrom app.
2. Install sql server express 2008.
3. Cerate backend database MyDatabase which relevant database objects;
tables, views, triggers, sps etc?

I need it to be as easy as possible for end user to install the app.

Many Thanks

Regards


From: kevinp on 19 Mar 2010 17:12
A quick Google search brought up this as well as many more:

http://www.databasejournal.com/features/mssql/article.php/3611426/SQL-Server-2005---Unattended-installation---Part-I.htm

I would suggest an installation DVD with an autorun where the user
could click on 1. Install Database, 2. Install Program, etc.


On Fri, 19 Mar 2010 14:46:50 -0000, "John" <info(a)nospam.infovis.co.uk>
wrote:

>Hi
>
>I have a winform app with sql server backend. How can I create a deployment
>package which when run by the end user does the following;
>
>1. Install front end vb winfrom app.
>2. Install sql server express 2008.
>3. Cerate backend database MyDatabase which relevant database objects;
>tables, views, triggers, sps etc?
>
>I need it to be as easy as possible for end user to install the app.
>
>Many Thanks
>
>Regards
>
From: Gregory A. Beamer on 22 Mar 2010 13:53


"John" <info(a)nospam.infovis.co.uk> wrote in message
news:eNezBM3xKHA.3408(a)TK2MSFTNGP06.phx.gbl...
> Hi
>
> I have a winform app with sql server backend. How can I create a
> deployment package which when run by the end user does the following;
>
> 1. Install front end vb winfrom app.
> 2. Install sql server express 2008.
> 3. Cerate backend database MyDatabase which relevant database objects;
> tables, views, triggers, sps etc?
>
> I need it to be as easy as possible for end user to install the app.

The .NET installer technology allows you to

a) bootstrap installs (SQL Express, for example)
b) Run scripts

If you need something more configurable, you will have to go with another
installer technology or download tools to whack at the MSI to customize it.
I would suggest googling deployment, installer projects, and the like. You
also need to look at bootstrapping SQL Express; any decent site will also
show you how to check if it is installed so you don't try to install it
again.

--
Peace and Grace,
Greg

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

************************************************
| Think outside the box! |
************************************************

From: Paul Pedersen on 22 Mar 2010 14:03
That brings up a question I've had. If Express (or full SQL Server) is
already installed, is it good practice to use the one that's already there,
or install a new Express instance?

I'm concerned about permission and login conflicts, and also the possibility
that the program that originally installed Express might uninstall it some
day.




"Gregory A. Beamer" <NoSpamMgbworld(a)comcast.netNoSpamM> wrote in message
news:0FDF8E2F-092A-476B-AC35-8A49D9760D7A(a)microsoft.com...
>
>
> "John" <info(a)nospam.infovis.co.uk> wrote in message
> news:eNezBM3xKHA.3408(a)TK2MSFTNGP06.phx.gbl...
>> Hi
>>
>> I have a winform app with sql server backend. How can I create a
>> deployment package which when run by the end user does the following;
>>
>> 1. Install front end vb winfrom app.
>> 2. Install sql server express 2008.
>> 3. Cerate backend database MyDatabase which relevant database objects;
>> tables, views, triggers, sps etc?
>>
>> I need it to be as easy as possible for end user to install the app.
>
> The .NET installer technology allows you to
>
> a) bootstrap installs (SQL Express, for example)
> b) Run scripts
>
> If you need something more configurable, you will have to go with another
> installer technology or download tools to whack at the MSI to customize
> it. I would suggest googling deployment, installer projects, and the like.
> You also need to look at bootstrapping SQL Express; any decent site will
> also show you how to check if it is installed so you don't try to install
> it again.
>
> --
> Peace and Grace,
> Greg
>
> Twitter: @gbworld
> Blog: http://gregorybeamer.spaces.live.com
>
> ************************************************
> | Think outside the box! |
> ************************************************



From: Gregory A. Beamer on 30 Mar 2010 15:38


"Paul Pedersen" <nospam(a)no.spam> wrote in message
news:OVpd3neyKHA.5936(a)TK2MSFTNGP04.phx.gbl...
> That brings up a question I've had. If Express (or full SQL Server) is
> already installed, is it good practice to use the one that's already
> there, or install a new Express instance?

I would say 9 times out of 10, you are better to just install a database,
but it may be more like 99 out of 100 or more.

> I'm concerned about permission and login conflicts, and also the
> possibility that the program that originally installed Express might
> uninstall it some day.

When you do an install with a database, ask for user credentials for install
and you can overcome the issues you talk about. With a previously installed
version of SQL or SQL Express, you can, with proper permissions, use the
attach stored procedure and actually ship with an MDB. This is faster than
using a full install script. You may still need the install script as a
backup (if nothing else, dump it so the user can install the database). If
you go that route, a config utility to change the connection string in the
config file.

--
Peace and Grace,
Greg

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

************************************************
| Think outside the box! |
************************************************

 | 
Pages: 1
Prev: Image not getting loaded from My.Resources
Next: Managing delays on dropdown or on tooltopexts