Re: MSDE licensing rules
From: Andrea Montanari (andrea.sqlDMO_at_virgilio.it)
Date: 04/27/04
- Next message: AldexLen: "Re: Problems using the MSDE Deployment toolkit"
- Previous message: Andrea Montanari: "Re: MSDE Installation Parameters"
- In reply to: Willem van den Broek: "Re: MSDE licensing rules"
- Next in thread: Willem van den Broek: "Re: MSDE licensing rules"
- Reply: Willem van den Broek: "Re: MSDE licensing rules"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 27 Apr 2004 12:54:22 +0200
hi Willem,
"Willem van den Broek" <willem@chsd.nl> ha scritto nel messaggio
news:OIz8cKDLEHA.2396@TK2MSFTNGP12.phx.gbl...
> Hi Andrea (and everybody else who wants to respond),
>
> Thanks for your reply. Your pointer to SERVERPROPERTY is probably the best
> advice. One remark: the type is nvarchar(128).
>
> I'm developing an InnoSetup (I'm sure you know it), that has to handle the
> setups/updates of IE 6, MDAC 2.8, .NET Framework 1.1 and MSDE 2000A,
> depending on what type of setup the enduser wants (Workstation
(application
> only), Network (database only) or Stand-alone (application and database)),
> without having to bother the enduser with to many technical details. The
> average housewife (no offence), who is able to switch on a computer,
should
> be able to run the setup.
>
> The only problem I ran into was when to setup MSDE. I guess the best
> approach is to only install it, with an instancename, when there is no
> version of SQL Server available at all, or when SERVERPROPERTY('edition')
of
> a running version returns 'Desktop Engine'. I think it's not my
> responsebility when the enduser runs 'Developer Edition' or 'Enterprise
> Evaluation Edition'.
>
> I know multiple instances require more systemresource, but I have to
comply
> by the rule "Multiple vendors cannot share a copy of MSDE", in case an
> instance of MSDE is already running. I wonder if other developers, who
> redistribute MSDE, take this in account?
>
> If someone thinks different, or has additional information, please let me
> know.
>
> Willem
personally I do install MSDE with a separate installer, which is a VB6 [
still =;-D ] app... it only installs the engine and not the app database(s),
which will be created and populated at first application run, connecting to
the SQL Server/MSDE instance specified in the app settings.
it prompt the user for all available parameters, presenting a list of all
available (if any) instances of SQL Server/MSDE, and those info are retrived
via SQL-DMO.
it's up to the user the choice of what to do... installing MSDE or not.. if
the user wants to, all user's choices are passed as command line parameters
to setup.exe boostrap installer.. but this is another story.
but, if it's me, I didn't like to have 10/11 running MSDE instances on my pc
becouse of 10/11 separate applications from different vendors... =;-) but
this is another story too...
-- Andrea Montanari (Microsoft MVP - SQL Server) http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0 (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface) --------- remove DMO to reply
- Next message: AldexLen: "Re: Problems using the MSDE Deployment toolkit"
- Previous message: Andrea Montanari: "Re: MSDE Installation Parameters"
- In reply to: Willem van den Broek: "Re: MSDE licensing rules"
- Next in thread: Willem van den Broek: "Re: MSDE licensing rules"
- Reply: Willem van den Broek: "Re: MSDE licensing rules"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
