Re: ver 2000 vs 2005

Well if you don't change the default instance they will both be listening on
1433 and who knows what you will get. You can't have two SQL Server
instances on the same server with the same port number.

--
Andrew J. Kelly SQL MVP


"Carlos" <ch_sanin@xxxxxxxxx> wrote in message
news:uIbBdK74FHA.2092@xxxxxxxxxxxxxxxxxxxxxxx
> No I did not. In reality I am trying to connect to one instace at any
> given time
> since I have the connection strings next to each other, I comment out the
> line that I do not wish to test, and uncomment the connection string
> for 2005. Kind of like this:
>
> //connection string for SQLSrvr2000
> //this.sqlConnection1.ConnectionString =
> "Server=xxx.xx.xx.xx;Database=myDB;User
> ID=myUID;Password=myPWD;Trusted_Connection=False";
>
> //connection string for SQLSrvr2005
> this.sqlConnection1.ConnectionString =
> "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User
> ID=myUID;Password=myPWD;Trusted_Connection=True";
>
>
> Thanks again for your help.
>
> Carlos
>
> "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message
> news:e0Pj$%2364FHA.2888@xxxxxxxxxxxxxxxxxxxxxxx
>> Did you change the port on the default (2000) instance to something other
>> than 1433?
>>
>> --
>> Andrew J. Kelly SQL MVP
>>
>>
>> "Carlos" <ch_sanin@xxxxxxxxx> wrote in message
>> news:%23KntJk64FHA.2092@xxxxxxxxxxxxxxxxxxxxxxx
>>> Hi Andrew,
>>>
>>> thank you for your prompt reply. I did assign a different port for the
>>> named instance in 2005. I am trying to use a connection string that
>>> already
>>> works in 2K by just changing to an already provided database, and
>>> including the named instance, and port number in the connection string.
>>> This is kind of how it looks like:
>>>
>>> this.sqlConnection1.ConnectionString =
>>> "Server=xxx.xx.xx.xx\\<myNamedServerInstance>,<port>;Database=AdventureWorks;User
>>> ID=myUID;Password=myPWD;Trusted_Connection=True";
>>>
>>> I am still no able to at least open the connection.. Any help is
>>> appreciated.
>>> Thanks in advance.
>>>
>>> Carlos.
>>>
>>>
>>> "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message
>>> news:%23hUsMqv4FHA.2548@xxxxxxxxxxxxxxxxxxxxxxx
>>>> You can not have both instances using port 1433. The default instance
>>>> which in your case is most likely the 2000 instance will have 1433.
>>>> The named instance (2005) will use a port other than 1433. Do not make
>>>> them both 1433.
>>>>
>>>> --
>>>> Andrew J. Kelly SQL MVP
>>>>
>>>>
>>>> "Carlos" <chsanin@xxxxxxxxxxxxx> wrote in message
>>>> news:uXRaTpo4FHA.2524@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> Hi all,
>>>>>
>>>>> I just installed version 2005, and it is co-existing with
>>>>> an instance of 2000. I am trying to test the connection string fro an
>>>>> ASP .Net page which works fine already in
>>>>> 2000. However it does not work in 2005.
>>>>> In 2005, I went to configuration Manager/Protocols/TCP IP, and entered
>>>>> 1433 as the port in IP1, IP2, and IP3
>>>>> Then, in my connection string I just changes the databasename to point
>>>>> to 'AdventureWorks' instead of
>>>>> the DB that I used for 2K. The connection could not be openned. I also
>>>>> configured the user id, and password the same way as I have in 2K, and
>>>>> re-started the engine.
>>>>>
>>>>> At this point I do not know what else should I do.
>>>>>
>>>>> Any help will be appreciated.
>>>>>
>>>>> Thanks in advance,
>>>>>
>>>>> Carlos
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: different environment fails to fill a dataset
    ... If not you may want to add it to the connection string ... Andrew J. Kelly SQL MVP ... a single database. ...
    (microsoft.public.sqlserver.clients)
  • Re: ver 2000 vs 2005
    ... if you are going to specify the port and an ip address. ... Andrew J. Kelly SQL MVP ... >> Andrew J. Kelly SQL MVP ... >>> line that I do not wish to test, and uncomment the connection string ...
    (microsoft.public.sqlserver.connect)
  • Re: ver 2000 vs 2005
    ... Did you change the port on the default instance to something other ... Andrew J. Kelly SQL MVP ... and port number in the connection string. ... >> Andrew J. Kelly SQL MVP ...
    (microsoft.public.sqlserver.connect)
  • Re: ver 2000 vs 2005
    ... Andrew J. Kelly SQL MVP ... I am trying to test the connection string fro an ASP ... > In 2005, I went to configuration Manager/Protocols/TCP IP, and entered ...
    (microsoft.public.sqlserver.connect)
  • Re: ver 2000 vs 2005
    ... line that I do not wish to test, and uncomment the connection string ... > Andrew J. Kelly SQL MVP ... I did assign a different port for the ... >> including the named instance, and port number in the connection string. ...
    (microsoft.public.sqlserver.connect)