Enterprise Manager Port?

What port does SQL Server Enterprise Manager need open to connect to a
remote database? I'm not finding documentation on this.
Shabam
By default SQL Server uses port 1433. This is the port Enterprise Manager
will attempt to use when connecting to SQL Server. If the SQL Server you are
attaempting to connect to was set up to use another port you will need to
use the SQL Server Client Network Utility to set up an alias to the port
being used.
Hope this helps
John
"Shabam" wrote:

> What port does SQL Server Enterprise Manager need open to connect to a
> remote database? I'm not finding documentation on this.
>
>
|||It's up to the Remote SQL Server and the client network utility. By default
named pipes and TCP port 1433 (UDP port 1434 is a broadcast port for server
name but not necessary) Check the SQL Error log on the remote server to see
what protocol it is listening on. Then check the SQL Server client network
utility on your workstation. Create an alias if necessary.
"Shabam" <chalupa@.yomama-nospam.com> wrote in message
news:3bidnexq3dFh_6TfRVn-gg@.adelphia.com...
> What port does SQL Server Enterprise Manager need open to connect to a
> remote database? I'm not finding documentation on this.
>

Enterprise Manager Port?

What port does SQL Server Enterprise Manager need open to connect to a
remote database? I'm not finding documentation on this.Shabam
By default SQL Server uses port 1433. This is the port Enterprise Manager
will attempt to use when connecting to SQL Server. If the SQL Server you are
attaempting to connect to was set up to use another port you will need to
use the SQL Server Client Network Utility to set up an alias to the port
being used.
Hope this helps
John
"Shabam" wrote:
> What port does SQL Server Enterprise Manager need open to connect to a
> remote database? I'm not finding documentation on this.
>
>|||It's up to the Remote SQL Server and the client network utility. By default
named pipes and TCP port 1433 (UDP port 1434 is a broadcast port for server
name but not necessary) Check the SQL Error log on the remote server to see
what protocol it is listening on. Then check the SQL Server client network
utility on your workstation. Create an alias if necessary.
"Shabam" <chalupa@.yomama-nospam.com> wrote in message
news:3bidnexq3dFh_6TfRVn-gg@.adelphia.com...
> What port does SQL Server Enterprise Manager need open to connect to a
> remote database? I'm not finding documentation on this.
>

Enterprise Manager Port?

What port does SQL Server Enterprise Manager need open to connect to a
remote database? I'm not finding documentation on this.Shabam
By default SQL Server uses port 1433. This is the port Enterprise Manager
will attempt to use when connecting to SQL Server. If the SQL Server you are
attaempting to connect to was set up to use another port you will need to
use the SQL Server Client Network Utility to set up an alias to the port
being used.
Hope this helps
John
"Shabam" wrote:

> What port does SQL Server Enterprise Manager need open to connect to a
> remote database? I'm not finding documentation on this.
>
>|||It's up to the Remote SQL Server and the client network utility. By default
named pipes and TCP port 1433 (UDP port 1434 is a broadcast port for server
name but not necessary) Check the SQL Error log on the remote server to see
what protocol it is listening on. Then check the SQL Server client network
utility on your workstation. Create an alias if necessary.
"Shabam" <chalupa@.yomama-nospam.com> wrote in message
news:3bidnexq3dFh_6TfRVn-gg@.adelphia.com...
> What port does SQL Server Enterprise Manager need open to connect to a
> remote database? I'm not finding documentation on this.
>

Enterprise Manager 7 -> SQL 2000

Is there documentation anywhere stating that SQL 7 Enterprise Manager / Query Analyzer cannot connect to a SQL 2000 server?

We are in the process of upgrading our SQL serves to SQL Server 2k (only 1 out of 10 left). We have one site that uses Query Analyzer from SQL 7 to connect and run some sql scripts, as well as Enterprise Manager.

I vaguely remember reading that you can't connect to 7 from 2k. Just need to forward on the documentation to someone...

ThanksIt worked great for me. But not 6.5.|||Originally posted by barneyrubble318
It worked great for me. But not 6.5.

Well I don't know how you did it. But, when I try to add a SQL Server 2000 Server Registration to my SQL 7 Enterprose Manager I get the following error.

A connection could not be established to SQLSERVER123 - You must upgrade your SQL Enterprise Manager and SQL DMO (SQLOLE) to SQL Server 2000 (SQLDMO) to connect to this server..|||hello,
u r Going to get an error when u r connecting thru enterprise manager,
but u donot have any problem if u connect thru query analyzer(isqlw)

pavan|||Refer to the discussion under this link. (http://www.sqlmag.com/Forums/messageview.cfm?catid=13&threadid=7478)