Hello!
I was wondering if I need to install something on the client in order to
establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have ADO
2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL Server
2005?
Thanks,
IgorHi
It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but you
will not be able to use the new datatypes that SQL Server 2005 has
introduced.
The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
function of the Operating System to update them.
The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
"Provider=SQLNCLI"
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ulvm%23pcCGHA.2300@.TK2MSFTNGP15.phx.gbl...
> Hello!
> I was wondering if I need to install something on the client in order
> to establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have
> ADO 2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL
> Server 2005?
> Thanks,
> Igor
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> Hi
> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
> you will not be able to use the new datatypes that SQL Server 2005 has
> introduced.
> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
> function of the Operating System to update them.
> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
> "Provider=SQLNCLI"
>
This is not quite right. MDAC is part of the operating system, but SQL
Native Client is not.
The SQL Native Client is a seperate install. It is included in the SQL
Server distribution and available here:
http://msdn.microsoft.com/data/sqlnative/default.aspx
There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
(deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
(SQLNCLI). SQLNCLI is the best, but you must install it.
SQL Native Client also has a new ODBC driver.
David|||David,
I am able to connect to SQL Server 2005 using SQL Native Client but
I got en error 'Server unavailable or access denied ...' when trying to
connect using Microsoft OLE DB provider for SQL Server. I am trying to
connect by setting up properties of UDL file on the same box where SQL
Server is installed. Did I get it right that I have to install latest
drivers on client computers from the link your provided?
Thanks,
Igor
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
>> you will not be able to use the new datatypes that SQL Server 2005 has
>> introduced.
>> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
>> function of the Operating System to update them.
>> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
>> "Provider=SQLNCLI"
> This is not quite right. MDAC is part of the operating system, but SQL
> Native Client is not.
>
> The SQL Native Client is a seperate install. It is included in the SQL
> Server distribution and available here:
> http://msdn.microsoft.com/data/sqlnative/default.aspx
> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
> (SQLNCLI). SQLNCLI is the best, but you must install it.
> SQL Native Client also has a new ODBC driver.
> David
>|||David,
I wa able to connect by enabling remote connections using Surface Area.
Thanks,
Igor
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23t2FLdxCGHA.724@.TK2MSFTNGP10.phx.gbl...
> David,
> I am able to connect to SQL Server 2005 using SQL Native Client but
> I got en error 'Server unavailable or access denied ...' when trying to
> connect using Microsoft OLE DB provider for SQL Server. I am trying to
> connect by setting up properties of UDL file on the same box where SQL
> Server is installed. Did I get it right that I have to install latest
> drivers on client computers from the link your provided?
> Thanks,
> Igor
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
>> you will not be able to use the new datatypes that SQL Server 2005 has
>> introduced.
>> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
>> function of the Operating System to update them.
>> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
>> "Provider=SQLNCLI"
>>
>> This is not quite right. MDAC is part of the operating system, but SQL
>> Native Client is not.
>>
>> The SQL Native Client is a seperate install. It is included in the SQL
>> Server distribution and available here:
>> http://msdn.microsoft.com/data/sqlnative/default.aspx
>> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
>> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
>> (SQLNCLI). SQLNCLI is the best, but you must install it.
>> SQL Native Client also has a new ODBC driver.
>> David
>
Showing posts with label establish. Show all posts
Showing posts with label establish. Show all posts
Tuesday, March 27, 2012
Friday, February 17, 2012
Connecting (ODBC) to SQL 2005 Express from different domain with trust
Hi!
I am trying to establish connection from different domain using ODBC driver with no luck!
I am able to do it within my domain from any place, but it fails from outside. I have two-ways trust established between domains. Users are able to see and use resources both ways.
When I create ODBC it doesn't matter if I use SQL or Windows NT authenctication, I am getting error:
Connection Failed:
SQLState: '01000'
SQLServer Error: 11004
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Connection Open (getbyhostname()() )
Connectio Failed:
SQLState: '08001'
SQL Server Error: 11
I tried to set it with TCP Static Port or Dynamic. No difference.
What should I look into?
Any ideas? Any help?
Thanks.
Did you try using the ip address ? Maybe the name cannot be resolved ?
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Yes I tried. Does SQl 2005 Express have any limitations as far as Connections from other domains?
Any other ideas.
|||No, it don′t has such things. Is the server pingable ? SQL Server uses a dynamic port not he standard port. The SQL Server browser service will redirect incoming request to the appripiate dynamic port. Therefore the service has to be started on the server system. Did you check that ?
Jens K. Suessmeyer
http://www.sqlserver2005.de
I am able to ping server, able to access files on server using UNC.
SQL Server browser is running on my server. Everything is in place, yet I can't logon.
I tried setting up ODBC Data Source with both Windows NT and SQL account authentication with no luck.
SQL actually is letting me create login using user name from other domain. I can do Find and discover users from other domain.
When it gets to making connection with server from their side it just dont see it.
Is that possible that because server is installed as a named instance I am having that problem?
|||There has to be a firewall in between which block the traffic (bit not ICMP). Make sure you configured the firewall to let the appropiate ports open for connecting.
Jens K. Suessmeyer
http://www.sqlserver2005.de
Connecting (ODBC) to SQL 2005 Express from different domain with trust
Hi!
I am trying to establish connection from different domain using ODBC driver with no luck!
I am able to do it within my domain from any place, but it fails from outside. I have two-ways trust established between domains. Users are able to see and use resources both ways.
When I create ODBC it doesn't matter if I use SQL or Windows NT authenctication, I am getting error:
Connection Failed:
SQLState: '01000'
SQLServer Error: 11004
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Connection Open (getbyhostname()() )
Connectio Failed:
SQLState: '08001'
SQL Server Error: 11
I tried to set it with TCP Static Port or Dynamic. No difference.
What should I look into?
Any ideas? Any help?
Thanks.
Did you try using the ip address ? Maybe the name cannot be resolved ?
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Yes I tried. Does SQl 2005 Express have any limitations as far as Connections from other domains?
Any other ideas.
|||No, it don′t has such things. Is the server pingable ? SQL Server uses a dynamic port not he standard port. The SQL Server browser service will redirect incoming request to the appripiate dynamic port. Therefore the service has to be started on the server system. Did you check that ?
Jens K. Suessmeyer
http://www.sqlserver2005.de
I am able to ping server, able to access files on server using UNC.
SQL Server browser is running on my server. Everything is in place, yet I can't logon.
I tried setting up ODBC Data Source with both Windows NT and SQL account authentication with no luck.
SQL actually is letting me create login using user name from other domain. I can do Find and discover users from other domain.
When it gets to making connection with server from their side it just dont see it.
Is that possible that because server is installed as a named instance I am having that problem?
|||There has to be a firewall in between which block the traffic (bit not ICMP). Make sure you configured the firewall to let the appropiate ports open for connecting.
Jens K. Suessmeyer
http://www.sqlserver2005.de
Connecting (ODBC) to SQL 2005 Express from different domain with trust
Hi!
I am trying to establish connection from different domain using ODBC driver with no luck!
I am able to do it within my domain from any place, but it fails from outside. I have two-ways trust established between domains. Users are able to see and use resources both ways.
When I create ODBC it doesn't matter if I use SQL or Windows NT authenctication, I am getting error:
Connection Failed:
SQLState: '01000'
SQLServer Error: 11004
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Connection Open (getbyhostname()() )
Connectio Failed:
SQLState: '08001'
SQL Server Error: 11
I tried to set it with TCP Static Port or Dynamic. No difference.
What should I look into?
Any ideas? Any help?
Thanks.
Did you try using the ip address ? Maybe the name cannot be resolved ?
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Yes I tried. Does SQl 2005 Express have any limitations as far as Connections from other domains?
Any other ideas.
|||No, it don′t has such things. Is the server pingable ? SQL Server uses a dynamic port not he standard port. The SQL Server browser service will redirect incoming request to the appripiate dynamic port. Therefore the service has to be started on the server system. Did you check that ?
Jens K. Suessmeyer
http://www.sqlserver2005.de
I am able to ping server, able to access files on server using UNC.
SQL Server browser is running on my server. Everything is in place, yet I can't logon.
I tried setting up ODBC Data Source with both Windows NT and SQL account authentication with no luck.
SQL actually is letting me create login using user name from other domain. I can do Find and discover users from other domain.
When it gets to making connection with server from their side it just dont see it.
Is that possible that because server is installed as a named instance I am having that problem?
|||There has to be a firewall in between which block the traffic (bit not ICMP). Make sure you configured the firewall to let the appropiate ports open for connecting.
Jens K. Suessmeyer
http://www.sqlserver2005.de
Subscribe to:
Posts (Atom)