connect to named instances

How can I connect to a named instance from a client. I believe the problem
is bcos of the port number.. When i connect to computername\instancename it
says SQL Server does not exist or access denied. However when i register an
alias in client network utility with the instance name and the actual port
number it works fine, but i have to use the alias.
Can i not register with the instance name directly without setting it up
thru the client network utility ? Please advice..
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.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:ud6L39KLEHA.2100@.TK2MSFTNGP10.phx.gbl...
> How can I connect to a named instance from a client. I believe the problem
> is bcos of the port number.. When i connect to computername\instancename
it
> says SQL Server does not exist or access denied. However when i register
an
> alias in client network utility with the instance name and the actual port
> number it works fine, but i have to use the alias.
> Can i not register with the instance name directly without setting it up
> thru the client network utility ? Please advice..
>
|||> 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/
|||Does that mean that with the latest MDAC, the client would dynamically
determine the port of the named instance ?
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:%23GGZf4LLEHA.3944@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
2.6
> 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/
>
|||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...[vbcol=seagreen]
2.6
> 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/
>
|||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[vbcol=seagreen]
> 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...
> 2.6
MDAC[vbcol=seagreen]
> before
some
>
|||It is indirectly documented here:
INF: How to Connect to an SQL Server 2000 Named Instance with the Previous
Version's Client Tools
http://support.microsoft.com/default...&Product=sql2k
The MORE INFORMATION section begins with a statement that MDAC 2.6 is
required to connect to a named instance in \\computer_name\instance_name
format. The article then goes on to describe a workaround.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:%23GGZf4LLEHA.3944@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
2.6
> 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/
>
|||Ah, I see, this wasn't really specified, as I use computername\instance_name
(not \\computername\instance_name) over TCP/IP all the time, and
http://www.aspfaq.com/2126 has recommended the \instance_name syntax since
long before MDAC 2.6 (1999 or 2000 sometime). I'm talking about connecting
to SQL Server from, for example, ASP or VB, over TCP/IP, not named pipes.
Sorry about the confusion.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:OJzZU3MLEHA.3808@.TK2MSFTNGP12.phx.gbl...
> It is indirectly documented here:
> INF: How to Connect to an SQL Server 2000 Named Instance with the Previous
> Version's Client Tools
> http://support.microsoft.com/default...&Product=sql2k
> The MORE INFORMATION section begins with a statement that MDAC 2.6 is
> required to connect to a named instance in \\computer_name\instance_name
> format. The article then goes on to describe a workaround.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
>
> "Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
> news:%23GGZf4LLEHA.3944@.tk2msftngp13.phx.gbl...
> 2.6
> before
>
|||Let me rephrase, 2000 sometime. I thought MDAC 2.6 was introduced much
later than SQL Server 2000, but I must be remembering incorrectly.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
|||2.6 was the release with RTM SQL 2000
--snip
Release Version Number
MDAC 2.6 RTM (2.60.6526.3), September 2000
Release Function
This release provides, directly to the public, the same version of MDAC
released with Microsoft SQL ServerT 2000.
--snip
Snipped from:
Release Manifest for MDAC 2.6 RTM (2.60.6526.3)
http://support.microsoft.com/default...tmmanifest.asp
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:%23TxVKBNLEHA.3012@.tk2msftngp13.phx.gbl...
> Let me rephrase, 2000 sometime. I thought MDAC 2.6 was introduced much
> later than SQL Server 2000, but I must be remembering incorrectly.
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
sqlsql