Re: Is it MSDE or SQLServer

• Previous message: dev: "Re: updating database"
• In reply to: JJ: "Re: Is it MSDE or SQLServer"
• Next in thread: JJ: "Re: Is it MSDE or SQLServer"
• Reply: JJ: "Re: Is it MSDE or SQLServer"
• Messages sorted by: [ date ] [ thread ]

Date: Mon, 3 May 2004 21:37:30 +0200

A possible full SQL Server could be either a default or a named instance. I would check an installed MSDE to
see if the registry will show whether it is an MSDE or not. If that info is available in the registry, just
iterate the reg keys and see whether there is a full version or not.

I don't have an MSDE available, but from looking at a dev edition install, there's a risk that you won't find
out from the reg keys. If that is the case, you either have to try to log on using Windows Authentication and
run SERVERPROPERTY (and if the login fails, let the user provide input), or just list the instances and let
the user specify what to do...

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"JJ" <jjjj@nospam.com> wrote in message news:uJ8DB8TMEHA.2532@TK2MSFTNGP10.phx.gbl...
> No, what I really want to do is find out if the "full" SQL Server is
> installed.
>
> If it is, the installer does not do anything with the database server - it
> installs some SQL scripts to create tables, but we leave it up to the end
> user's administrator to create the database and set up database security as
> they like.
>
> If it is not, then the installer installs MSDE in a named instance and
> creates the database and tables (just attaches a pre-built .mdf file).
>
> Basically, if they already have the "full" SQL Server installed, I don't
> want to touch it with my installer.  We are figuring (with the purpose of
> our particular situation, not in general) that if they have SQL Server
> installed, they know what they are doing and have preferences as to where
> they want their database to go, collation options, maintenance plans,
> security, etc. and don't want an automatic install that makes assumptions.
> So I was hoping to find a sure-fire way to tell if full SQL Server is
> installed.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in
> message news:O0$iYDRMEHA.268@TK2MSFTNGP11.phx.gbl...
> > My guess is that it is only created if a default instance is created. But,
> does it matter? In any event, you
> > want to enumerate the instance names so the user can select which instance
> to use for the app (if not
> > installing a new instance). Not?
> >
> > -- 
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> >
> >
> > "JJ" <jjjj@nospam.com> wrote in message
> news:%23xN2z8QMEHA.1312@TK2MSFTNGP12.phx.gbl...
> > > Thanks.
> > >
> > > But if another software package has installed MSDE2000 (under a named
> > > instance), won't the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
> root
> > > exist?  Or does that only get created when either SQL Server or MSDE is
> > > installed as a default instance?
> > >
> > > "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote
> in
> > > message news:endiTvGMEHA.2388@TK2MSFTNGP09.phx.gbl...
> > > > Here's the registry root for SQL Server for a default instance (and
> > > earlier versions)
> > > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
> > > >
> > > > And below is for the named instances:
> > > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
> > > >
> > > > Above should give you a starting point.
> > > > -- 
> > > > Tibor Karaszi, SQL Server MVP
> > > > http://www.karaszi.com/sqlserver/default.asp
> > > >
> > > >
> > > > "JJ" <jjjj@nospam.com> wrote in message
> > > news:OCf8aOrLEHA.340@TK2MSFTNGP11.phx.gbl...
> > > > > On a similar topic, is there a reliable way to tell if the "full"
> SQL
> > > Server
> > > > > is simply installed (not MSDE), perhaps through registry entries?
> I'd
> > > like
> > > > > to determine in my installer whether or not the user has the full
> SQL
> > > Server
> > > > > installed already and if they do, use that instead of installing
> MSDE.
> > > > >
> > > > >
> > > > > "Greg Low (MVP)" <greglow@lowell.com.au> wrote in message
> > > > > news:ugq1obqLEHA.2660@TK2MSFTNGP09.phx.gbl...
> > > > > > In addition to what James wrote, the SERVERPROPERTY(Edition)
> function
> > > > > would
> > > > > > probably give you a more direct (and system readable) option.
> > > > > >
> > > > > > HTH,
> > > > > >
> > > > > > -- 
> > > > > > Greg Low (MVP)
> > > > > > MSDE Manager SQL Tools
> > > > > > www.whitebearconsulting.com
> > > > > >
> > > > > >
> > > > > > "Erik Visser" <evisser@hotmail.com> wrote in message
> > > > > > news:c6t7ka$fvc1o$1@ID-206424.news.uni-berlin.de...
> > > > > > > > SELECT @@VERSION
> > > > > > >
> > > > > > > Yep, this works.
> > > > > > > Thanks!
> > > > > > >
> > > > > > > Erik
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

• Previous message: dev: "Re: updating database"
• In reply to: JJ: "Re: Is it MSDE or SQLServer"
• Next in thread: JJ: "Re: Is it MSDE or SQLServer"
• Reply: JJ: "Re: Is it MSDE or SQLServer"
• Messages sorted by: [ date ] [ thread ]