Re: connect to named instances

From: Dinesh T.K (tkdinesh_at_nospam.mail.tkdinesh.com)
Date: 04/28/04


Date: Thu, 29 Apr 2004 00:34:45 +0530

Hassan,

Try Component checker tool (url may wrap)
'MDAC Utility: Component Checker'
http://www.microsoft.com/downloads/details.aspx?familyid=8f0a8df6-4a21-4b43-bf53-14332ef092c9&displaylang=en

--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Hassan" <fatima_ja@hotmail.com> wrote in message
news:e5aRYEVLEHA.1156@TK2MSFTNGP09.phx.gbl...
> Any way to find out what version of MDAC I have ? Ive got SQL 2K Developer
> Edition with SP3a installed
>
> "Geoff N. Hiten" <SRDBA@Careerbuilder.com> wrote in message
> news:uJEdE6ULEHA.1052@TK2MSFTNGP12.phx.gbl...
> > MDAC 2.6 and higher can determine the port number from a
> > computername\instancename request.  2.5 and lower cannot.  You can
specify
> a
> > port number with any MDAC version if it makes you more comfortable.  If
> you
> > turn on port hiding on the server, you must use the port number.
> >
> > SQL uses port 1434 to handle name-port resolution.  That is where the
> > Slammer worm hit.
> >
> >
> > -- 
> > Geoff N. Hiten
> > Microsoft SQL Server MVP
> > Senior Database Administrator
> > Careerbuilder.com
> >
> > I support the Professional Association for SQL Server
> > www.sqlpass.org
> >
> > "Hassan" <fatima_ja@hotmail.com> wrote in message
> > news:%23R5K20TLEHA.3216@TK2MSFTNGP12.phx.gbl...
> > > So i have to specify the port number then to connect thru EM from a
> > client.
> > > Am i right ? I tried this computername\instancename,port and it worked
> > >
> > >
> > > "Geoff N. Hiten" <SRDBA@Careerbuilder.com> wrote in message
> > > news:u7SZgkMLEHA.2660@TK2MSFTNGP09.phx.gbl...
> > > > I am not sure it MDAC 2.6 is the breakover point, but it is around
> that
> > > > version.  I will try and see if I can find it.
> > > >
> > > > SQL listens on all IP addresses that exist at service startup.  Each
> > > > instance has its own port.  A clustered instance has its own IP
> address
> > > and
> > > > port number, since the IP address is unique to the virtual server.
> MDAC
> > > 2.6
> > > > and above does resolve names and port numbers automagically.
> > > >
> > > > GNH
> > > >
> > > >
> > > > "Hassan" <fatima_ja@hotmail.com> wrote in message
> > > > news:ejJR8QMLEHA.2692@tk2msftngp13.phx.gbl...
> > > > > From BOL "Each instance of Microsoft® SQL ServerT 2000 listens on
a
> > > unique
> > > > > set of network address so that applications can connect to
different
> > > > > instances"
> > > > >
> > > > > What does this mean ? What is this n/w address ? If i have 2
> > instances(
> > > > one
> > > > > default and the other named ) , what are the 2 network addresses ?
> It
> > > cant
> > > > > be IP right ? So what is it ? Thanks
> > > > >
> > > > > "Aaron Bertrand [MVP]" <aaron@TRASHaspfaq.com> wrote in message
> > > > > news:%23GGZf4LLEHA.3944@tk2msftngp13.phx.gbl...
> > > > > > > Your client system likely has an older version of MDAC.
Install
> > > MDAC
> > > > > 2.6
> > > > > > > or
> > > > > > > higher to connect to a named instance without requiring an
> alias.
> > > > > >
> > > > > > Is this documented somewhere Geoff?  I don't remember *exactly*
> when
> > > > MDAC
> > > > > > 2.6 was released, but I know I was able to connect to named
> > instances
> > > > > before
> > > > > > I ever worried about what version of MDAC was installed, and
that
> > was
> > > > some
> > > > > > time ago.
> > > > > >
> > > > > > -- 
> > > > > > Aaron Bertrand
> > > > > > SQL Server MVP
> > > > > > http://www.aspfaq.com/
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>


Relevant Pages

  • Re: connect to named instances
    ... I believe SP3a shipped with MDAC 2.7. ... I support the Professional Association for SQL Server ... > "Geoff N. Hiten" wrote in message ... >> port number with any MDAC version if it makes you more comfortable. ...
    (microsoft.public.sqlserver.server)
  • Re: Sql Server Agent (2000) erroring out on DTS Packages
    ... DTSRun: Package execution complete. ... and a problem with a missing MDAC dll. ... On Sql Server 7, this was SQLAgentCmdExec. ... Specified driver could not be loaded due to system error 126 (MERANT MSSS ...
    (microsoft.public.sqlserver.dts)
  • Re: connect to named instances
    ... Any way to find out what version of MDAC I have? ... Ive got SQL 2K Developer ... > port number with any MDAC version if it makes you more comfortable. ... > I support the Professional Association for SQL Server ...
    (microsoft.public.sqlserver.server)
  • Re: Any help here???
    ... > start looking for things that are non standard (like having MDAC installed). ... > Format your drive, do a new/clean install of XP, and go from there. ... >>> data provider is optimized for SQL Server. ... >>> I've never had any SQL Server connectivity problems since I've switch to ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: SQL server Login connection failed sqlstate 28000 sql server e
    ... mdac 2.8 - ran the mdac checker and everything is fine ... and reconnect to the sql server using odbc - dsn connection. ... Now when we make mods to the database, reconnect, then we get that error. ... please download Component Checker from the link below to make sure ...
    (microsoft.public.sqlserver.odbc)