Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dbthj
Posting Yak Master
143 Posts |
 Posted - 2009-06-10 : 10:41:03
|
| I am planning on putting a 2005 instance on a productionserver that already has an instance of SQL 2000.SQL 2000 listens on port 1433.If I set the SQL 2005 instance to listen on 1433, can that be a problem? I have tested this on a dev server and see no problem so far. |
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
Posted - 2009-06-10 : 10:49:58
|
are you sure you can have 2000 and 2005 listening to the same port without problem ?
KH[spoiler]Time is always against us[/spoiler] |
 |
|
|
dbthj
Posting Yak Master
143 Posts |
Posted - 2009-06-10 : 10:58:42
|
| No, but I can access them both thru 2000 Enterprise manager and 2005 ssms onthe server. And I can access them remotely (both as sql 2005 ssms registered servers.I am not an OS admin nor am I very Network savy, so I have no idea what problemsthis might present. Is there something I should test? Should I abandon the idea?Here is why I want to do this:I am upgrading a vendor product to sql2005. I want to do this on the existing server.Therefore both instances have to coexist for a while. I am guessing it will be easierto reconfigure the application to point to sql2005 if it has the same port. Just a guess. |
|
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
Posted - 2009-06-10 : 11:14:51
|
you can run the SQL Server Configuration Manager and see what's the PORT NO that the SQL 2005 is using. The installation default should be Dynamic Ports unless you change to fixed it at 1433.
KH[spoiler]Time is always against us[/spoiler] |
|
|
|
dinakar
Master Smack Fu Yak Hacker
2507 Posts |
Posted - 2009-06-10 : 15:10:05
|
quote:
Originally posted by dbthj
No, but I can access them both thru 2000 Enterprise manager and 2005 ssms onthe server. And I can access them remotely (both as sql 2005 ssms registered servers.I am not an OS admin nor am I very Network savy, so I have no idea what problemsthis might present. Is there something I should test? Should I abandon the idea?Here is why I want to do this:I am upgrading a vendor product to sql2005. I want to do this on the existing server.Therefore both instances have to coexist for a while. I am guessing it will be easierto reconfigure the application to point to sql2005 if it has the same port. Just a guess.
you can have multiple instances on same server, but not all listening on same port. Its best to assign fixed ports than let them all be dynamic. You can open up SQL error logs and look for the mesage "SQL Server.. is listening on port <>" to find out what port the instance is listening on. As khtan mentioned you can configure the port in config manager.Dinakar Nethi************************Life is short. Enjoy it.************************http://weblogs.sqlteam.com/dinakar/ |
|
|
|
|
|
|
|
|
2 Instances, Same Server, Same Port?