I'm trying to configure an alias for a sql2005 named instance on the
server.

My server has 2 instances:

sql2k default
"sql2005" named

One ip address: 192.168.0.15

I configure an alias in configuratin manager to the following

Alias Name: alias n
Port no:
Protocol: tcp/ip
Server: servername\instancename

I can connect to the alias from SQL Studio Manager on the server but as
soon as one of my devleopers tries to access it via their Manager, it
defaults to the sql2k default instance. If I specify
servername\instancename it works so something is wrong with the alias
config.

Does anyone have some thoughts on this?

Thanks.

i would think if you use tcp instead of named pipes,
then you must use a different port for the 2nd instance.
that's what i would do.

Blackgoo wrote:
> I'm trying to configure an alias for a sql2005 named instance on the
> server.
>
> My server has 2 instances:
>
> sql2k default
> "sql2005" named
>
> One ip address: 192.168.0.15
>
> I configure an alias in configuratin manager to the following
>
> Alias Name: alias n
> Port no:
> Protocol: tcp/ip
> Server: servername\instancename
>
> I can connect to the alias from SQL Studio Manager on the server but as
> soon as one of my devleopers tries to access it via their Manager, it
> defaults to the sql2k default instance. If I specify
> servername\instancename it works so something is wrong with the alias
> config.
>
> Does anyone have some thoughts on this?
>
> Thanks.
>

Aliases are defined on the client side. The client needs the
information that AliasN points to server 192.168.0.15

-Sue

On 20 Oct 2006 15:06:26 -0700, "Blackgoo"
<blackgoo@gmail.com> wrote:

>I'm trying to configure an alias for a sql2005 named instance on the
>server.
>
>My server has 2 instances:
>
>sql2k default
>"sql2005" named
>
>One ip address: 192.168.0.15
>
>I configure an alias in configuratin manager to the following
>
>Alias Name: alias n
>Port no:
>Protocol: tcp/ip
>Server: servername\instancename
>
>I can connect to the alias from SQL Studio Manager on the server but as
>soon as one of my devleopers tries to access it via their Manager, it
>defaults to the sql2k default instance. If I specify
>servername\instancename it works so something is wrong with the alias
>config.
>
>Does anyone have some thoughts on this?
>
>Thanks.

The SQL Server Browser Service resolves the instance names to the ports. Is
it running on the SQL Server computer? Try starting that service.
--
Rick Byham, MS
This posting is provided "AS IS" with no warranties, and confers no rights.

"Blackgoo" <blackgoo@gmail.com> wrote in message
news:1161381986.782005.172140@e3g2000cwe.googlegro ups.com...
> I'm trying to configure an alias for a sql2005 named instance on the
> server.
>
> My server has 2 instances:
>
> sql2k default
> "sql2005" named
>
> One ip address: 192.168.0.15
>
> I configure an alias in configuratin manager to the following
>
> Alias Name: alias n
> Port no:
> Protocol: tcp/ip
> Server: servername\instancename
>
> I can connect to the alias from SQL Studio Manager on the server but as
> soon as one of my devleopers tries to access it via their Manager, it
> defaults to the sql2k default instance. If I specify
> servername\instancename it works so something is wrong with the alias
> config.
>
> Does anyone have some thoughts on this?
>
> Thanks.
>

Sue,

I read this, what you suggested below, and I was wondering if you could
tell me what the client is--the user's/dev's computer that has the
tools installed on it?

Also, when they try connecting to the instance via alias name in a .net
application it doesn't work either so then how does configuring an
alias on that client change that?

Thanks.

Scott

Sue Hoegemeier wrote:
> Aliases are defined on the client side. The client needs the
> information that AliasN points to server 192.168.0.15
>
> -Sue
>
> On 20 Oct 2006 15:06:26 -0700, "Blackgoo"
> <blackgoo@gmail.com> wrote:
>
> >I'm trying to configure an alias for a sql2005 named instance on the
> >server.
> >
> >My server has 2 instances:
> >
> >sql2k default
> >"sql2005" named
> >
> >One ip address: 192.168.0.15
> >
> >I configure an alias in configuratin manager to the following
> >
> >Alias Name: alias n
> >Port no:
> >Protocol: tcp/ip
> >Server: servername\instancename
> >
> >I can connect to the alias from SQL Studio Manager on the server but as
> >soon as one of my devleopers tries to access it via their Manager, it
> >defaults to the sql2k default instance. If I specify
> >servername\instancename it works so something is wrong with the alias
> >config.
> >
> >Does anyone have some thoughts on this?
> >
> >Thanks.

Hi Scott,

The client is where the application or tools are located
that will be connecting to SQL Server. So my PC is the
client when I'm using the any of the tools to connect to SQL
Server. If I have some VB.Net application installed on my PC
and that app connects to SQL Server then my PC is the
client.
Does that clear it up at all?

-Sue

On 24 Oct 2006 23:41:57 -0700, "Blackgoo"
<blackgoo@gmail.com> wrote:

>Sue,
>
>I read this, what you suggested below, and I was wondering if you could
>tell me what the client is--the user's/dev's computer that has the
>tools installed on it?
>
>Also, when they try connecting to the instance via alias name in a .net
>application it doesn't work either so then how does configuring an
>alias on that client change that?
>
>Thanks.
>
>Scott
>
>Sue Hoegemeier wrote:
>> Aliases are defined on the client side. The client needs the
>> information that AliasN points to server 192.168.0.15
>>
>> -Sue
>>
>> On 20 Oct 2006 15:06:26 -0700, "Blackgoo"
>> <blackgoo@gmail.com> wrote:
>>
>> >I'm trying to configure an alias for a sql2005 named instance on the
>> >server.
>> >
>> >My server has 2 instances:
>> >
>> >sql2k default
>> >"sql2005" named
>> >
>> >One ip address: 192.168.0.15
>> >
>> >I configure an alias in configuratin manager to the following
>> >
>> >Alias Name: alias n
>> >Port no:
>> >Protocol: tcp/ip
>> >Server: servername\instancename
>> >
>> >I can connect to the alias from SQL Studio Manager on the server but as
>> >soon as one of my devleopers tries to access it via their Manager, it
>> >defaults to the sql2k default instance. If I specify
>> >servername\instancename it works so something is wrong with the alias
>> >config.
>> >
>> >Does anyone have some thoughts on this?
>> >
>> >Thanks.

The browsing service is running on both the server and the dev's
workstation. What am I missing?

Rick Byham, MS wrote:
> The SQL Server Browser Service resolves the instance names to the ports. Is
> it running on the SQL Server computer? Try starting that service.
> --
> Rick Byham, MS
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Blackgoo" <blackgoo@gmail.com> wrote in message
> news:1161381986.782005.172140@e3g2000cwe.googlegro ups.com...
> > I'm trying to configure an alias for a sql2005 named instance on the
> > server.
> >
> > My server has 2 instances:
> >
> > sql2k default
> > "sql2005" named
> >
> > One ip address: 192.168.0.15
> >
> > I configure an alias in configuratin manager to the following
> >
> > Alias Name: alias n
> > Port no:
> > Protocol: tcp/ip
> > Server: servername\instancename
> >
> > I can connect to the alias from SQL Studio Manager on the server but as
> > soon as one of my devleopers tries to access it via their Manager, it
> > defaults to the sql2k default instance. If I specify
> > servername\instancename it works so something is wrong with the alias
> > config.
> >
> > Does anyone have some thoughts on this?
> >
> > Thanks.
> >

This should work. The only additional idea I have, is since you are running
in a mixed SQL Server 2000 and SQL Server 2005 network, did the developer
computer use the SQL Server 2005 Configuration Manager to create the alias.
The SQL Server 2000 tools won't work for SQL Server 2005.
--
Rick Byham, MS
This posting is provided "AS IS" with no warranties, and confers no rights.

"Blackgoo" <blackgoo@gmail.com> wrote in message
news:1164931359.650442.193750@h54g2000cwb.googlegr oups.com...
> The browsing service is running on both the server and the dev's
> workstation. What am I missing?
>
> Rick Byham, MS wrote:
>> The SQL Server Browser Service resolves the instance names to the ports.
>> Is
>> it running on the SQL Server computer? Try starting that service.
>> --
>> Rick Byham, MS
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Blackgoo" <blackgoo@gmail.com> wrote in message
>> news:1161381986.782005.172140@e3g2000cwe.googlegro ups.com...
>> > I'm trying to configure an alias for a sql2005 named instance on the
>> > server.
>> >
>> > My server has 2 instances:
>> >
>> > sql2k default
>> > "sql2005" named
>> >
>> > One ip address: 192.168.0.15
>> >
>> > I configure an alias in configuratin manager to the following
>> >
>> > Alias Name: alias n
>> > Port no:
>> > Protocol: tcp/ip
>> > Server: servername\instancename
>> >
>> > I can connect to the alias from SQL Studio Manager on the server but as
>> > soon as one of my devleopers tries to access it via their Manager, it
>> > defaults to the sql2k default instance. If I specify
>> > servername\instancename it works so something is wrong with the alias
>> > config.
>> >
>> > Does anyone have some thoughts on this?
>> >
>> > Thanks.
>> >
>