Page 1 of 1
Port not supported for SQL Server
Posted: Wed 11 Jul 2007 14:50
by archie
Hi,
I'm trying to connect to a Microsoft SQL Server on a non-standard port, but I experience problems when I'm specifying the port. When I try to connect I receive the following error: Port not supported for SQL Server.
Why isn't it possible to specify a port number? Is there any other way for me to specify the port, because we have numerous situations where the SQL Server isn't listening on the default port.
Thanks.
Posted: Wed 11 Jul 2007 15:37
by Alexey
We are going to fix this.
Look forward to hearing from me again.
Posted: Thu 12 Jul 2007 07:02
by archie
Great
Does this mean all providers will support different ports to be specified from now on? From what we've seen only MySQL and Postgre could have a port specified.
Any idea when all this will be ready?
Thanks!
Posted: Thu 12 Jul 2007 07:32
by Alexey
What do you mean "all providers"? MySQLDirect .NET, PostgreSQLDirect .NET and OraDirect .NET has this connection attribute. So we are going to fix this only in UniDirect .NET when using it with standard provider for MS SQL Server.
Posted: Thu 12 Jul 2007 07:45
by archie
Yes, perfect. Thanks.
Posted: Thu 12 Jul 2007 14:45
by Alexey
We have analyzed the problem and found out that special keyword for port is not needed. You should set it like this:
Code: Select all
provider=SQL Server;Data Source=server2, 1433;Initial Catalog=Test;User ID=sa;
where 1433 is your port number.
Posted: Mon 16 Jul 2007 06:53
by archie
Ok, but could you fix the problem anyway? The idea of UniDirect is to be a transparent layer to all DBMS, it'd be kind of stupid to have to deal with this Port anomaly for MSSQL specifically. It'd be better if we could just set the Port property of the UniConnection and your library would take care of setting up the connection string properly.
Posted: Mon 16 Jul 2007 08:29
by Alexey
OK, we will do it for you.
Posted: Tue 04 Sep 2007 13:43
by archie
Is there any news regarding an update of UniDirect? It has been a while and we've never heard anything about the next update.
Posted: Wed 05 Sep 2007 08:32
by Alexey
We haven't fix this yet, unfortunately.