specify port using SQLNative Client ODBC - by JasonJason

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


0
0
Sign in
to vote
ID 252812 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 1/19/2007 5:55:57 AM
Access Restriction Public

Description

With the ss2000 odbc connection, you could specify the port through a configuration screen.  With ss2005 odbc client that screen no longer exists.  It would be nice if it still did for use when connecting to sql server on the non-default port.
Sign in to post a comment.
Posted by Microsoft on 3/23/2007 at 3:14 PM
This is still possible. The SS2000 ODBC driver provided a direct link to cliconfg from the ODBC administrator to define a server alias with the same name as the server. SQL Server Native Client does not have the same link from DSN admin, but you can still use cliconfg from the Start/Run menu to define aliases manually, and this will allow you to define an alias with the same name as the server name in a DSN and then configure protocol/TCP port or other connection options.
Posted by Microsoft on 1/22/2007 at 5:59 PM
This is still possible. The SS2000 ODBC driver provided a direct link to cliconfg from the ODBC administrator to define a server alias with the same name as the server. SQL Server Native Client does not have the same link from DSN admin, but you can still use cliconfg from the Start/Run menu to define aliases manually, and this will allow you to define an alias with the same name as the server name in a DSN and then configure protocol/TCP port or other connection options.