Non-Standard Port with SQL Server ODBC

Why does the SQL Server ODBC Connection page not mention any example of using a non-standard port?

I was incorrectly trying to use the "Port" attribute as "Port=x" but that does not work.
It would be helpful to see that non-standard ports (anything other than 1433) should be appended to the server attribute value after a comma.

Bad: Server=servername;Port=portnumber;
Good: Server=servername,portnumber;

0
edit delete
are you sure?
asked David Garcia

0 answers

Post an answer but please log in first

Post Answer
  1. Please log in to post answer

Similar Questions

Tagsfor this question

Forumall questions