wsakp.blogg.se

It took the ODBC driver a little over 3 minutes to call the 91000 rows whereas it took the IBMDASQL driver over 7 minutes running the same query.

I tested the difference between the two drivers by doing a select * on a large table and compared the time it took to complete using the IBMDASQL driver versus the ODBC driver. I am actually not using the IBMDASQL driver anymore for my servers as I noticed there was quite a difference in response time versus using ODBC (which as a side note is not available in 64 bit servers). When I connect to SQL Server using the Windows Authenticated login, the exact same query against the linked server fails with the messages above. So, when I connect to SQL Server using the SQL Authenticated login, a query against the linked server works. The Windows Authenticated login refers to a domain login having administrator priviledges on the local SQL Server box. In order to analyze the problem, I created one sysadmin SQL Server authenticated login and one sysadmin Windows Authenticated login. The linked server security is defined to login to the IBM iSeries using a fixed user and password regardless of the login using the linked server.

Access denied.Ĭannot get the column information from OLE DB provider "IBMDASQL" for linked server "DB2ARUBA". The OLE DB provider "IBMDASQL" for linked server "DB2ARUBA" reported an error. I started converting our developers to Windows Authentication and access to the linked server is denied when used from a Windows Authenticated session. The linked server has been defined and working for months when used from a SQL Server authenticated session. I have a linked server defined on a SQL Server 2005 SP2 standard edition server using the IBMDASQL OLEDB driver.