SQL Sever Enterprise Manager Connection Syntax

[DXD]

What is the syntax to connect to a specific instance of SQL on a server with a specific port using Enterprise Manager.

I've tried

server\instance,port and I've tried server,port\instance but hasn't worked.

Or is port 1435 blocked?

[canislupusyo]

SB should make a list of ports being blocked becuase i know they block Standard SQL/Netbios/Samba ports but who know's what else they block

[DXD]

I know they block SQL ports but SQL ports are 1433 and 1434 that's why I was using 1435 but was woundering if that was blocked too. I just tried 1450 and that didn't work either.

[canislupusyo]

here is a clip from one of my scripts
sConnectionString = "User ID=<username>;Password =<strong password>;Initial Catalog=pubs;Data Source=myServer,<port>";

so it is server,port

[DXD]

But that is for your script I'm talking about inside SQL Enterprise Manager.

[canislupusyo]

it should automaticly change the connection settings to the port you change it to when you restart the SQL service.

Where are you changing the port at ?

[DXD]

I guess I'm not being clear enough.

The server has an instance of MSDE called HELM and the server has an instance of SQL SERVER called SQL01.

I want to connect to the server from my home pc to the SQL01 instance of SQL SERVER on a specific port since the default SQL Server ports are blocked.

When you register a new SQL server in Enterprise manager you normally type SERVERNAME,PORT so that it knows what port to use. But I don't not know how to specify what instance to connect to.

[KyleMulligan]

I just checked and you don't have an SQL server listening on port 1435 at the ip your domain name resolves to. Are you positive the SQL Server service is running at the time you are trying to connect?

[DXD]

I actually figured out my problems late last night.

First off I forgot to install SP3a that was the root of the issue.

Each SQL Server instance must run on a different port if you plan to connect to it remotly.

Using the Server Network Utility you need to pick the instance you want to connect to and assign it an unblocked port.

Next you need to make sure your port is not blocked for TCP through your firewall.

Next you need to use the Client Network Utility on your pc that you plan to connect from and create an alias that points to the server the instance and the port.

Now once that all is done you can register the SQL Server instance in Enterprise Manager using the Alias that shows up in your Server list.

Now that I know anyone needing help with this just let me know.

[TangentWizard]

Have you looked at the new MS SQL Server Express which is Microsofts new free SQL it's excellent and does away with the silly restrictions although it only address's the first 1gb of memory and 1 cpu which is ideal for SB Servers. And a Breeze to Install.

Been using/testing it for the past month it's excellent and faster. As about everthing that SQL 2005 will have.

[DXD]

Yes actually I did look at that, and would of gone with it but it's still only Beta 2.

For a production environment I try to stay away from Beta's especially since my largers clients are all using SQL I'd hate to piss them off :)