While I am not a super network guy, I'd like to think I am not an idiot when it comes to networks. That being the case, the first thing I did was specify the server as serverName:portNumber. Imagine my surprise when this did not work. Now imagine my surprise when I discovered the solution: serverName,portNumber.
This also worked when connecting to the SQL 2K server using Enterprise Manager.
I have never heard of using a comma to delimit the server name from the port number, but now I know, and so do you.
For the record, I asked a DBA and a network guy, and neither of them suggested using the comma.
13 comments
Now the real tough one - has anyone figured out how to copy tables from one database to another without losing Primary Key definitions and defaults?
Justin
I use that as well in Enterprise Manager.
Though,I was using the free version of SQL Studio, and there was no equivalent, that I could find, for SQL 2005.
Assuming you are using DTS, you have to "Copy objects between SQL server databases", then makes sure you turn on "include extended properties" on the last page. You may want to turn off the copying of users and roles, that usually doesn't work for me.
thanks
an ID10t
further problem though,
I need replication to occur on the
same port as well. When I try to add
my subscribers using server,port SSMS tells
me that you can't use an IP Address or Alias
and must use the instance name. Does anyone
know how to push a subscribtion to another
port?
After reading your blog I used a comma et voila! It works!
Thankyouthankyouthankyouthankyouthankyou
I was using freeproxy to tunnel connections to the sql server and I was getting errors when sql manager tried to connect to proxy using different port.