any computer actually that they will use to use the same database.
I need an easy way for my low-tech users to stick in my install CD, select
Server installation , and I offer a named instance of SQL server using SQL
Security... Also needs to create a new copy of the database, offer them a
prompt for the DB password and more.
I need this to be as easy as possible.
What is the best route in doing this?
If it requires an DBA or high-tech user to install, then that will rule out
most of my clients, and make distributing this app and using MSDE not a very
wise choice.
Thanks for any help,
ShaneShane,
Your app sound very similar to ours and so do your users :> )
This is what I have just done and it works very well.
Our install software is InstallShield DevStudio 9.1 and it allows you to
conditionally install MSDE 2000. BTW it does not allow you to conditional
install MSDE 1.0. It also allows you to put in an instance name if you want
one.
So all I did was change the setup type screen that normally reads 'typical',
'minimum' and 'custom' to read 'server', 'client' and 'custom'. A Server
selection installs MSDE plus the client components and a Client selection
will not install MSDE.
As for the database itself I scripted all the schema, you can do that thru
EM, and enough table data to get the application going. ie Default Data.
You can run this either via a vbScript or batch file using the osql command.
We elected to script the data because some of our customers already have SQL
and they often want to use that, especially if there are large numbers of
users. It also gets over the problem of a customer having SQL, wanting to
use it, and their sort order is different to yours.
In the batch or vbscript you could offer prompts for sa password. Install
MSDE with a blank or known password, run the database scripts, ask for a new
password, change it and your done.
There's no easy way to do what you want, ie giving the user options like
passwords instance names etc., and I've tried them all. If you didn't want
to have the flexibility and wanted a set install then Installshield would do
it all. Just click on setup and it would install your app, msde, make the
instance, have a set sa password and attach or run a batch file to install
your databases. But, you have to make the decision.
Hope this helps.
Greg
--
greghines@.bigfoot.com.NOSPAM
Remove NOSPAM when replying
"SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:eCkwq$QEEHA.628@.TK2MSFTNGP10.phx.gbl...
> I have a 5 user app that uses MSDE as the database. It is run on a
"SERVER"
> any computer actually that they will use to use the same database.
> I need an easy way for my low-tech users to stick in my install CD, select
> Server installation , and I offer a named instance of SQL server using SQL
> Security... Also needs to create a new copy of the database, offer them a
> prompt for the DB password and more.
> I need this to be as easy as possible.
> What is the best route in doing this?
> If it requires an DBA or high-tech user to install, then that will rule
out
> most of my clients, and make distributing this app and using MSDE not a
very
> wise choice.
> Thanks for any help,
> Shane
>|||Thanks Greg.
Does the msde 2000 copy you are installing have SP3 already applied?
I installed on my dev machine using the one from VB.NET I think.
Also when you mention scripting with vbscript...is that from inside of
Install Shield or are you running that from wsh or something?
Since .NET comes with a decent installer I was thinking about making it with
that. Don't have a lot of funds to buy another installer.
But I could have two separate ones. One that installs the app, then another
that installs MSDE, and maybe have them both run from a webpage that starts
with autorun. Let them type sa password to use in the webpage and somehow
use javascript or something to run the actual MSDE with the appropriate
params. I don't know that might be hard. These are some things I have
thought of.
I know we are licensed to use MSDE for owning .NET Pro. There seem to be
several flavors of MSDE, and seems I saw one that would install with SP3
included. Guess I need to research some more.
At present, I have a new fire to put out. Did a restore on the database and
now ADO.NET fails to connect.
So can't do much else until I resolve this.
I am just gathering information on each area that I need or will need in
order to distribute the project easily.
Thanks for all your advice.
It is very helpful to hear from you,
Shane
"Greg Hines" <greghines@.bigfoot.com.NOSPAM> wrote in message
news:1080108879.380672@.gw-gos.nlc.net.au...
> Shane,
> Your app sound very similar to ours and so do your users :> )
> This is what I have just done and it works very well.
> Our install software is InstallShield DevStudio 9.1 and it allows you to
> conditionally install MSDE 2000. BTW it does not allow you to conditional
> install MSDE 1.0. It also allows you to put in an instance name if you
want
> one.
> So all I did was change the setup type screen that normally reads
'typical',
> 'minimum' and 'custom' to read 'server', 'client' and 'custom'. A Server
> selection installs MSDE plus the client components and a Client selection
> will not install MSDE.
> As for the database itself I scripted all the schema, you can do that thru
> EM, and enough table data to get the application going. ie Default Data.
> You can run this either via a vbScript or batch file using the osql
command.
> We elected to script the data because some of our customers already have
SQL
> and they often want to use that, especially if there are large numbers of
> users. It also gets over the problem of a customer having SQL, wanting to
> use it, and their sort order is different to yours.
> In the batch or vbscript you could offer prompts for sa password. Install
> MSDE with a blank or known password, run the database scripts, ask for a
new
> password, change it and your done.
> There's no easy way to do what you want, ie giving the user options like
> passwords instance names etc., and I've tried them all. If you didn't
want
> to have the flexibility and wanted a set install then Installshield would
do
> it all. Just click on setup and it would install your app, msde, make the
> instance, have a set sa password and attach or run a batch file to install
> your databases. But, you have to make the decision.
> Hope this helps.
> Greg
> --
> greghines@.bigfoot.com.NOSPAM
> Remove NOSPAM when replying
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:eCkwq$QEEHA.628@.TK2MSFTNGP10.phx.gbl...
> "SERVER"
select
SQL
a
> out
> very
>|||One Question, sp2kdesksp3.exe
I ran it to install to a local folder.
This says to have an install complete with SP3.
Is this the one I should use for install?
If so, then I just need a front end and to prompt for sa password and I am
set. Then using the scripting and such that you spoke of with OSQL to
install the database and such.
Thanks,
Shane
I downloaded a file called,
"Greg Hines" <greghines@.bigfoot.com.NOSPAM> wrote in message
news:1080108879.380672@.gw-gos.nlc.net.au...
> Shane,
> Your app sound very similar to ours and so do your users :> )
> This is what I have just done and it works very well.
> Our install software is InstallShield DevStudio 9.1 and it allows you to
> conditionally install MSDE 2000. BTW it does not allow you to conditional
> install MSDE 1.0. It also allows you to put in an instance name if you
want
> one.
> So all I did was change the setup type screen that normally reads
'typical',
> 'minimum' and 'custom' to read 'server', 'client' and 'custom'. A Server
> selection installs MSDE plus the client components and a Client selection
> will not install MSDE.
> As for the database itself I scripted all the schema, you can do that thru
> EM, and enough table data to get the application going. ie Default Data.
> You can run this either via a vbScript or batch file using the osql
command.
> We elected to script the data because some of our customers already have
SQL
> and they often want to use that, especially if there are large numbers of
> users. It also gets over the problem of a customer having SQL, wanting to
> use it, and their sort order is different to yours.
> In the batch or vbscript you could offer prompts for sa password. Install
> MSDE with a blank or known password, run the database scripts, ask for a
new
> password, change it and your done.
> There's no easy way to do what you want, ie giving the user options like
> passwords instance names etc., and I've tried them all. If you didn't
want
> to have the flexibility and wanted a set install then Installshield would
do
> it all. Just click on setup and it would install your app, msde, make the
> instance, have a set sa password and attach or run a batch file to install
> your databases. But, you have to make the decision.
> Hope this helps.
> Greg
> --
> greghines@.bigfoot.com.NOSPAM
> Remove NOSPAM when replying
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:eCkwq$QEEHA.628@.TK2MSFTNGP10.phx.gbl...
> "SERVER"
select
SQL
a
> out
> very
>|||Shane,
The MSDE 2000 Merge Module with DevStudio 9 does have SP3 already applied,
so you don't have to worry about applying it.
DevStudio allows either Installshield Scripting or a VBScript to be run from
inside Installshield. So you can do things like:-
a) Installer selects the type of setup. Typical, Min. Custom etc.
b) This opens your custom dialog with say some questions to answer. eg sa
password. Their responses are stored in variables.
c) They click on Next to proceed with the installation.
Or you could do:-
a) Install a default installation of MSDE 2000 SP3 with a blank sa password.
b) After setup finishes run either a vbScript or Installshield script that
asks for an sa password.
c) Within that script run an osql command to change the sa password.
If you want to go with MSDE 2000 then there is no reason to have 2 install
apps. DevStudio 9 will do all you want and more.
As I said earlier I've been installing MSDE 1.0 and more recently MSDE 2000
with our apps. for sometime now and the MSDE 2000 Merge Module with
DevStudio is by far the easiest as it can be conditionally installed. If
you want to go with MSDE 1.0 then it has to be script driven as MSDE 1.0
cannot be conditionally installed.
Hope I've been helpful.
Regards,
Greg
--
greghines@.bigfoot.com.NOSPAM
Remove NOSPAM when replying
"SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:epF$cacEEHA.3788@.TK2MSFTNGP10.phx.gbl...
> Thanks Greg.
> Does the msde 2000 copy you are installing have SP3 already applied?
> I installed on my dev machine using the one from VB.NET I think.
> Also when you mention scripting with vbscript...is that from inside of
> Install Shield or are you running that from wsh or something?
> Since .NET comes with a decent installer I was thinking about making it
with
> that. Don't have a lot of funds to buy another installer.
> But I could have two separate ones. One that installs the app, then
another
> that installs MSDE, and maybe have them both run from a webpage that
starts
> with autorun. Let them type sa password to use in the webpage and somehow
> use javascript or something to run the actual MSDE with the appropriate
> params. I don't know that might be hard. These are some things I have
> thought of.
> I know we are licensed to use MSDE for owning .NET Pro. There seem to be
> several flavors of MSDE, and seems I saw one that would install with SP3
> included. Guess I need to research some more.
> At present, I have a new fire to put out. Did a restore on the database
and
> now ADO.NET fails to connect.
> So can't do much else until I resolve this.
> I am just gathering information on each area that I need or will need in
> order to distribute the project easily.
> Thanks for all your advice.
> It is very helpful to hear from you,
> Shane
>
> "Greg Hines" <greghines@.bigfoot.com.NOSPAM> wrote in message
> news:1080108879.380672@.gw-gos.nlc.net.au...
conditional
> want
> 'typical',
selection
thru
Data.
> command.
> SQL
of
to
Install
> new
> want
would
> do
the
install
> select
> SQL
them
> a
rule
a
>|||Thanks Greg.
I appreciate the info.
Since I don't have a budget to buy additional setup software right now.
I chose to create a prompting VC++ app to do my server setup.
It prompts for all the needed info, creates the setup.ini file in a temp dir
and then calls the setup.exe program for MSDE passing the right parameters,
then it calls a batch file passing that info, so that I can create the
structure with calls to osql with scripts and then will copy the data as
soon as I learn how.
How can I copy data into the new database?
Is BCP the only option. Seems complicated. I was hoping for an easier way
to do that. The amount of data needing to be copied is less than 100 rows
in 8 tables.
Thanks,
Shane
"Greg Hines" <greghines@.bigfoot.com.NOSPAM> wrote in message
news:1080511923.196920@.gw-gos.nlc.net.au...
> Shane,
> The MSDE 2000 Merge Module with DevStudio 9 does have SP3 already applied,
> so you don't have to worry about applying it.
> DevStudio allows either Installshield Scripting or a VBScript to be run
from
> inside Installshield. So you can do things like:-
> a) Installer selects the type of setup. Typical, Min. Custom etc.
> b) This opens your custom dialog with say some questions to answer. eg sa
> password. Their responses are stored in variables.
> c) They click on Next to proceed with the installation.
> Or you could do:-
> a) Install a default installation of MSDE 2000 SP3 with a blank sa
password.
> b) After setup finishes run either a vbScript or Installshield script that
> asks for an sa password.
> c) Within that script run an osql command to change the sa password.
> If you want to go with MSDE 2000 then there is no reason to have 2 install
> apps. DevStudio 9 will do all you want and more.
> As I said earlier I've been installing MSDE 1.0 and more recently MSDE
2000
> with our apps. for sometime now and the MSDE 2000 Merge Module with
> DevStudio is by far the easiest as it can be conditionally installed. If
> you want to go with MSDE 1.0 then it has to be script driven as MSDE 1.0
> cannot be conditionally installed.
> Hope I've been helpful.
> Regards,
> Greg
> --
> greghines@.bigfoot.com.NOSPAM
> Remove NOSPAM when replying
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:epF$cacEEHA.3788@.TK2MSFTNGP10.phx.gbl...
> with
> another
> starts
somehow
be
> and
to
> conditional
you
Server
> selection
> thru
> Data.
have
> of
wanting
> to
> Install
a
like
> would
> the
> install
message
using
> them
> rule
not
> a
>
No comments:
Post a Comment