Re: SQL 2000 & Multiple Instances....

Tech-Archive recommends: Fix windows errors by optimizing your registry

Only one instance can use a port at a time. So if they are both configured to use port 1433, you cannot use both databases at once.
Probably not what you want. Better change the DEV instance to something else.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Joe" <Joe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:C554AFD9-5AD9-4DF4-A6B7-FBAAA43CCDE7@xxxxxxxxxxxxxxxx
I have a question about multiple SQL Instances running on the same server.

I inherited a SQL Server that had been setup with two SQL Instances (Prod &
Dev).
Both instances are setup to use the default port (1433). There is an
application
server that needs to connect to the DEV instance via ODBC, but they are unable
to connect and only connect to the Prod instance.

Is there a way to have them both answer on 1433? I thought that was why you
have a named instance (One is DBSRV1\DBSRV1_PROD and the other is
DBSRV1\DBSRV1_DEV). I know it works if I change the port of the DEV instance,
but that would involve a lot of firewall changes that the client is not
happy about
performing.

It would be best if we can have both instances working on the same port.

Any pointers would be appreciated.

.

Relevant Pages

  • Re: ADP problems after SQL 2005 Upgrade
    ... Use the SQL Server Configuration Manager to create aliases; ... each port can be associated only with a single instance. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • [NT] Microsoft SQL Server 2000 Unauthenticated System Compromise
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Microsoft's database server SQL Server 2000 exhibits two buffer-overrun ... clients connecting to TCP port 1433 or both. ... This message is a single byte packet, ...
    (Securiteam)
  • Re: Do SqlServer 2000 & SqlServer 2005 co-exist
    ... Either SQL Server 2000 or SQL Server 2005. ... So you have to move one of them to another port. ... You could allow an program exception in your firewall instead of a port number exception. ... I understand that you can connect to SQL 2000 named instance on the local ...
    (microsoft.public.sqlserver.setup)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... Only one instance of SQL Server can use TCP port 1434. ... You may find it easier to use SQL Server Configuration Manager ... 2008 will be a named instance ... you will have to open those as exceptions in the firewall. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL 200 Dev edition on workgroup will not connect
    ... I have been using sql server for about 8 years but mainly working with sql 2000. ... know your experience level with SQL Server and yes, sometimes things being messy but letting a SQL Server instance to accept remote connections and uninstalling it are generally straightforward tasks to perform. ... I suggest you to check for the dynamic port number that your SQL Server graps. ... Write down the port number in the "TCP Dynamic Ports" property and then run a Command Prompt and see if this port is bening listened. ...
    (microsoft.public.sqlserver.connect)