Hi,
When distributing an application that uses MSDE, should you install
your application databases into a named instance or into the default
instance? Are there any guidelines on when to create a named instance
versus using the default one?
Thanks in advance.
Sincerely,
Dan
hi Dan,
"Dan" <ddeward@.msn.com> ha scritto nel messaggio
news:686970bc.0406141634.30e23b96@.posting.google.c om...
> Hi,
> When distributing an application that uses MSDE, should you install
> your application databases into a named instance or into the default
> instance? Are there any guidelines on when to create a named instance
> versus using the default one?
you usually have to ask your user... since MSDE is now free, you are not
obliged from Miscrosoft to create a new instance for each ISV relased
application...
but ISVs can "protect" with a personal EULA asserving their installed
instance only to their application...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message news:<2j852iFuc642U1@.uni-berlin.de>...
> hi Dan,
> "Dan" <ddeward@.msn.com> ha scritto nel messaggio
> news:686970bc.0406141634.30e23b96@.posting.google.c om...
> you usually have to ask your user... since MSDE is now free, you are not
> obliged from Miscrosoft to create a new instance for each ISV relased
> application...
> but ISVs can "protect" with a personal EULA asserving their installed
> instance only to their application...
Andrea,
I wasn't even aware of the earlier ISV requirement. Your suggestion
of asking the user makes sense. I will try into incorporate "freedom
of choice" in my setup.
Many thanks for your reply.
Sincerely,
Dan
|||There is still the legal requirement that each software company has to
use/install its own instance.
I suggest you do that to prevent confusion: one instance name for all MSDE
deployments with all your apps.
Jan
"Dan" <ddeward@.msn.com> wrote in message
news:686970bc.0406151557.18a33cdf@.posting.google.c om...
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:<2j852iFuc642U1@.uni-berlin.de>...
> Andrea,
> I wasn't even aware of the earlier ISV requirement. Your suggestion
> of asking the user makes sense. I will try into incorporate "freedom
> of choice" in my setup.
> Many thanks for your reply.
> Sincerely,
> Dan
|||hi Jan,
"Jan Doggen" <j.doggen@.BLOCKqsa.nl> ha scritto nel messaggio
news:%23BzqIn6UEHA.1164@.tk2msftngp13.phx.gbl...
> There is still the legal requirement that each software company has to
> use/install its own instance.
> I suggest you do that to prevent confusion: one instance name for all MSDE
> deployments with all your apps.
I've been told by Microsoft representative that this is no more an issue
becouse of the new "free" nature of MSDE...
it's no more mandatory that every separate ISV has it's own separate
instance, but every ISV can force it's own intalled instance not to serve
other ISV applications...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Sunday, February 19, 2012
Distributing application that use MSDE
Labels:
application,
database,
databases,
defaultinstance,
distributing,
installyour,
instance,
microsoft,
msde,
mysql,
named,
oracle,
server,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment