Linked server using ASEOLEDB

Hello.
Has anyone managed to get a linked server working between SQL 2008R2 and Sybase ASE 15.7 using the SAP/Sybase OLE DB driver and not using an ODBC DSN?
I've tried what seems like every combination of parameters to create the linked server both through the GUI and using sp_addlinkedserver, all to no avail.
If you could supply an example sp_addlinkedserver call that would be really helpful.
Thanks.

Hi Hedgehog,
According to your description, you need to create a linked server to Sybase by using ASE OLEDB provider, right?
If in this case, you need to install the DataDirect OLEDB Provider for Sybase on the machine running SQL Server. And you need to create and configure a Data Source before creating a linked server. Here is a blog which describes how to create a linked
server in SQL Server Sybase ASEdatabase using OLEDB provider.
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/11/12/how-to-create-a-linked-server-in-sql-server-2005-for-sybase-ase-12-5-database-using-datadirect-s-odbc-driver-and-oledb-provider.aspx
Regards,
Charlie Liao
TechNet Community Support

Similar Messages

Linked server using kerberos working fine then after inacitive for 10 minutes start receiving the anonymous logon error

Linked server using kerberos working fine but after leaving the session inactive for 10 minutes is startin to fall down to ntlm and receive the anonymous logon error

we are connecting to SQL mgmt studio app published on citrix, using Windows authentication and Kerberos to forward the credentials to the linked servers and avoid the double hop issue, that part is working fine, we already have the Constrained
delegation, SPNs and Active directory settings for the Service accounts and the authentication is working, we can connect to the linked servers without errors, it's only whe the Session get idle when we faced the issue, the citrix team already have verifyed
any timeout setting and they mentioned there is no 10 minute timout setting anywhere, we also looked at the Kerberos AD Global policy settings to see if maybe the kerberos service ticket was expiring, but the configured values are Maximum lifetime
for service ticket 600 minutes Maximum lifetime for user ticket 10 hours Maximum lifetime for user ticket renewal 7 days, if you have any other suggestion please let me know.

Linked server using kerberos working fine then after inactive for 10 minutes start receiving the anonymous logon error

Linked server using kerberos working fine then after inactive for 10 minutes start receiving the anonymous logon error

Hi,
This Could be a double hop problem or some thing could have gone wrong with your SPN
This could also be non trusted Service Account under which your SQL Server is running
Check the following links
http://blogs.technet.com/b/askds/archive/2008/06/13/understanding-kerberos-double-hop.aspx
http://blogs.msdn.com/b/sql_protocols/archive/2006/12/02/understanding-kerberos-and-ntlm-authentication-in-sql-server-connections.aspx
https://technet.microsoft.com/en-us/library/cc739474(v=ws.10).aspx
Hope this helps
Thanks
Bhanu

MS SQLServer Linked Server using Instant Client?

Does anyone have an example of setting up a linked server in SQLServer using instant client ODBC?

user11273096 wrote:
Hi All,
PLease need help urgently....
Have issue of connecting to a remote oracle server after following several tutorial online from step A-Z. http://www.dbatoolz.com/t/installing-oracle-instantclient-basic-and-instantclient-sqlplus-on-win32.html
I am the DBA that installed the remote oracle too so every information are right.Either you are mistaken or Oracle is in error.
I doubt Oracle mis-reports reality!
>
These are the errors: ORA-12154 or ORA-12560 TNS: protocol adapter error.ORA-12154 ALWAYS only occurs on SQL Client & no SQL*Net packets ever leave client system
ORA-12154 occurs when client requests a connection to some DB server system using some connection string.
The lookup operation fails because the name provided can NOT be resolved to any remote DB.
The analogous operation would be when you wanted to call somebody, but could not find their name in any phonebook.
The most frequent cause for the ORA-12154 error is when the connection alias can not be found in tnsnames.ora.
The lookup operation of the alias can be impacted by the contents of the sqlnet.ora file; specifically DOMAIN entry.

Trying to create a linked server to a remote 3rd party server using an AD group

I am the DBA at our organization so I have full authority to all of our local SQL Server databases but we have data in a remote 3rd party SQL Server database that is only read-only. The 3rd party has granted the read only privileges to one of our AD
groups - let's call it mydomain\adgroup1. I would like to create a linked server from one of our local SQL Servers to the remote database. I'm not sure how to do this.
I have set the AD group up as a login and a user in my local database. When I try to create the link, I used the mydomain\adgroup1 as the local login and, since the same credentials exist in the remote server, I checked the impersonate box and click
OK but I get "mydomain\adgroup1 is not a valid login or you do not have permission". Is it possible to create a linked server using an AD group? As of now, we only have the AD group permissions in the remote database. We could probably
request a single SQL Server account to be created on the remote side and we could create the same on our side, but we are trying to keep things as simple and transparent as possible (and we would really like to move more toward AD security and away
from individual users in the db).
Can anyone give me advice on how to get these two SQL Servers linked?

From your description, you likely want to implement Windows authentication for linked server, which requires to implement Kerberos constrained delegation.
I would recommend the following link to get started:
How to Implement Kerberos Constrained Delegation with SQL Server 2008 (https://msdn.microsoft.com/en-us/library/ee191523%28SQL.100%29.aspx?f=255&MSPPError=-2147217396
-Raul Garcia
SQL Server Security
This posting is provided "AS IS" with no warranties, and confers no rights.

UCCX 10.1 - Linked Server - Copying HR data to external SQL Server for reporting

I have a customer that is migrating from UCCX 7 to UCCX 10. They currently have a 2008 SQL Server R2 that they use for custom reports. They have a package that runs nightly to copy relevant data from UCCX 7 to the their server and then run reports daily against that database.   Pretty easy when everything is in MS SQL.  My plan was to set up a linked server in SQL 2008 to the UCCX server. This would allow me to easily run a query against Informix and move the data over as before. However, I am having problems adding the linked server.
I have installed the Informix drivers (both 32 and 64 bit) during the troubleshooting.
The DSN is created and connects to UCCX just fine.
When I attempt to add the linked server using 64 bit driver DSN I get the following:
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "UCCX101".
OLE DB provider "MSDASQL" for linked server "UCCX101" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "UCCX101" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "UCCX101" returned message "[Informix][Informix ODBC Driver][-11302] Insufficient Connection information was supplied". (.Net SqlClient Data Provider)
When I attempt to add the linked server using the 32 bit driver DSN I get the following:
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "32UCCX101".
OLE DB provider "MSDASQL" for linked server "32UCCX101" returned message "[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application". (Microsoft SQL Server, Error: 7303)
It appears to me there is a 32/64 bit conflict no matter route I go.
Can anyone tell me what I am missing?
Is there a better approach to take to achieve the ultimate goal?
Any suggestions are greatly appreciated.
TIA
John

I have created linked servers on an SQL2K box that points back to CCX. First off, you have to set the password for the UCCX HR user to some known value.
exec sp_dropserver 'fonccx9_01', 'droplogins'
EXEC sp_addlinkedserver
@server='fonccx9_01', -- Name of the Linked Server, when it is created.
@srvproduct='Microsoft OLE DB Provider for ODBC', -- OLE DB Provider.
@provider='MSDASQL', -- Provider_name.
@datasrc ='fonccx9-01', -- DSN Name of the ODBC Data Source.
@provstr= -- ODBC Connection String.
'Driver={IBM Informix ODBC};Server=fonccx9_01_uccx;Database=db_cra; Uid=uccxhruser; Pwd=Some-Password;'
EXEC sp_addlinkedsrvlogin
    @rmtsrvname = 'fonccx9_01',
    @useself = 'FALSE',
    @rmtuser = 'uccxhruser',
    @rmtpassword = 'Some-Password'
Note that the server name is "fonccx9-01", but the dash is an illegal character in the server name, so you have to change that to an underscore. You still have to manually build the ODBC data source on the box where you are trying to create the linked server.

OLEDB provider VFPOLEDB for linked server returned message "Invalid path or file name"

Hello,
I'm hoping someone can shed some light on this. I'd researched this error for days, reading all the post in this forum, however none of them address my issue.
We use VFP 9 .dbf tables (free tables). I setup a linked server to query the tables. As first we were not able to view the tables in SQL Server Mgmt Studio (MSMS) until I sorted out the permissions. I can query the tables if I copy over
to the server so they are local tables. However, across the network I am continually getting the error above and the following error:
"Cannot initialize the data source object of OLE DB provider VFPOLEDB for linked server XXX."
Here are the steps I've performed...
Installed a 32 bit instance of SQL Server Express 2008 R2 using Windows Authentication on server 2 (the 64 bit instance could not see the VFP OLE DB provider, as we all know, because the provider is only 32 bit)
Installed the latest VFP OLE DB from http://www.microsoft.com/en-us/download/details.aspx?id=14839.
In the VFPOLEDB provider, I enabled Nested queries, Level zero only, Allow inprocess, and Supports 'Like' operator.
Setup a linked server using the following query:
EXEC master.dbo.sp_addlinkedserver
@server = N'LinkedAC',
@srvproduct = N'Visual FoxPro 9',
@provider = N'VFPOLEDB',
@datasrc = N'"\\server1\share\TIW\KOKAC"',
@provstr = N'VFPOLEDB.1'
At first I could not view the tables when expanding default>Tables, it failed due to a "catastrophic failure". That can't be good ;-). After digging around, I surmised it was because I'd set the SQL Instance to run as NT Authority\NetworkService.
I created a new user, LinkedVFP, and added to the SQL Instance (using Windows Authentication), mapped the user to the master database with the db_datareader role. I also added the LinkedVFP user to the network share. I was then able to browse
the tables in MSMS and query the data when local, but still not across the network.
I'm using Crystal Reports to try and query the data from my local workstation using SELECT * FROM OPENQUERY(mylinkedserver, 'select * from table1'). This produces the two errors I mentioned above.
To clarify, the VFP tables are on server 1 and the linked server is on server 2. I've read about service account delegation, but unclear if this is the issue. I went into our domain controller (neither server 1 or 2), AD User and Computers, and
for server 2 I enabled 'Trust this computer for delegation to any service (Kerberos only)'.
Can anyone shed some light on this for me?
Thanks!
Aaron McVanner

Hi Aaron,
Thank you for your question. I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support

Linked server works for sa but not for user

I have a linked server to an Oracle database. It works fine for me logged in as DBA but not for the user. The linked server uses the same account regardless of who's using it.
When the user tries it the following error is thrown:
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server
I have granted public access to MSDB and execute on the xp_prop_oledb_provider object to the user.

this link should give all the connection string to sql server
http://www.connectionstrings.com/sql-server/
but can you verify if your application is really using that connection file ? try running trace alongside and try to connect to the database.. so do you atleast see a call from this config file with username - myapplication??
Hope it Helps!!

SQL Server 2K "Linked Server" to Oracle 9i Release 2 via "Oracle Provider

Hi,
I'm trying to set up a SQL Server 2000 "Linked Server" to Oracle 9i Release 2 via "Oracle Provider for OLE DB". I have downloaded and installed "Oracle Provider for OLE DB Release 9.2.0.2.0"
My SQL*Net alias/datasource in tnsnames.ora works (It passes the test in "Net 9i Configuration Assistant", I can connect from SQL*Plus, and I can get a Linked server going with the "Microsoft OLE DB Provider for Oracle").
When I set up my Linked Server with Oracle Provider for OLE DB, I need to supply the following three fields (with description from the read-only field at the bottom of the "Linked Server Properties)
Product name: (The product name is the OLE DB data source to add as a linked server.)
Data source: (The data source is usually the name of the server or filename.)
Provider string: (This is the entire provider string.)
Here is my tnsnames.ora entry that works as described above (names may have been changed to protect the innocent)...
PROD9I.XYZ.LOCAL =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = nn.nn.nn.nn)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = PROD.ora2.xyz.mno.com)
With every combination of values I have tried for these fields, when I try to use the Linked Server I get this error message...
Could not create an instance of OLE DB provider 'OraOLEDB.Oracle'.
OLE DB error trace [Non-interface error: CoCreate of DSO for OraOLEDB.Oracle returned 0x80040154].
Any help would be greatly appreciated
Thank you,
Daniel Jameson

Thanks Norman.
Well, I've made it a step closer. I uninstalled everything Oracle from my machine and reinstalled the 9i stuff, including the Oracle OLE DB Provider. Now, after I set up the linked server, and I try to view the Tables or Views under the Linked Servers, I get this error message...
Error 7399: OLE DB provider 'OraOLEDB.Oracle' reported an error.
OLE DB error trace [OLE/DB Provider 'OraOLEDB.Oracle' IDBINitialize::Initialize returned 0x80004005: ].
Does anyone have any idea what this is about? My other Linked Server using the same Oracle SQL*Net alias, but using the Microsoft OLE DB Provider, works fine.

SQL to Oracle Linked Server

I am trying to create a linked server from SQL2000 to Oracle9i.
i have done followings:
Install Oracle9i client on sql server machine.
Create a tnsname entry for my oracle database.
Created a linked server using following query:
exec sp_addlinkedserver 'ORA_HIPPOCRT',
'Oracle', 'MSDAORA', 'HIPPOCRT'
exec sp_addlinkedsrvlogin 'ORA_HIPPOCRT',
false, NULL, 'HR', 'password'
But when I query the data as follows:
SELECT * FROM ORA_HIPPOCRT..HR.EMPLOYEES
I get following errors:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation.
Provider is unable to function until these components are installed.]
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ].
What I am doing wrong?

I can get this to work using OPENQUERY() i.e.
select * from OPENQUERY(andyh, 'select * from TRAINDB.LINKEDSERVERDATATYPETEST')
To me though this has bodge written all over it.
Anyone out there with advise for me?
thanks.

SQL linked server twice as slow in Windows 7 as XP

We have a transaction based synchronization from SQL Server to Oracle, i.e. both must commit or rollback in one distributed transaction. We achieved this using MSSQL Linked Server using the Oracle Provider for OLE DB and triggers running openquery for speed.
The SQL Sever 2008 was on XP (doesn't need a server) and the Oracle 11g was on Red Hat 5EL. In testing from the first trigger firing to the last trigger finishing, a save test took ~11 Seconds, not perfect but acceptable. Yet when we moved to Windows 7 this time rose to 19 Seconds.
We contacted Microsoft support and they seen to thing it is a multi platform issue. So to prove them wrong we created an oracle DB on a Windows 7 system and ran the tests again, same issue. They will not look into the issue without us paying for premium support at an hourly rate, due to the Oracle DB. So we created one more test environment to try to prove it was a Microsoft issue and not an Oracle driver issue we created 2 SQL servers and ran tests to see if we got the same issue. We got the following results, which seems to point the finger at the Oracle OLE Driver on Win 7:
Windows XP sync to Windows 7:
SQL Server to Oracle = ~8 seconds
SQL Server to SQL Server = ~6.5 seconds
Windows 7 sync to Windows 7:
SQL Server to Oracle = ~19 seconds
SQL Server to SQL Server = ~5.5 seconds
Has anybody else found this issue and if so have they found a cause?
We Have run NetMon and analysed the results and the packets seem to take twice as long in Win 7 as Win XP. This seemed to point to a network issue, but does not explain why 100% Microsoft is faster when synchronising Win 7 to Win 7, as opposed to Win XP to Win 7.
I get the feeling the issue lies somewhere in the changes that were made by Microsoft in Vista in the networking protocols and configuration, causing a side affect in the OLE Driver. It could be that the driver works, but needs to be tuned with the new networking protocols from Microsoft.
We have tried countless network settings, even the ones suggestions from MS Support made no difference at all.
Edited by: 925129 on 03.04.2012 03:57
Corrected a couple of types

Hi Greg,
Thanks for the answer, sorry for the late reply, I was away for Easter.
What we have done is to alter the triggers to record their names, start and end times to an SQL Server table. I delete the contents of the table then run a test and run several queries to analyse the trigger data. the difference between the min start time and the max end time is how we get the total time. We run many queries over the data. I can send you the table DDL and some test run results DML, as well as, the queries I use to analyse the results.
On top of this test we have run Microsoft's NetMon to analyse the network traffic and there it is clear that the packets take roughly twice as long in Win 7 as in Win XP, both in 32-bit and 64-bit OS versions. I know there has been some major network changes after Win XP and Microsoft are convinced this is an Oracle issue. The same OLE Driver is used for both Win 7 and Win XP OS's (excluding the one for 32-bit and one for 64-bit) and my guess is something needs to be tuned for the networking in Win 7. We have really tested this so much over the last 2 months and tried all kinds of network setting tuning in windows but nothing has worked at all.
After creating an SQL DB to act in the place Oracle DB, the same issue was not present, so it really is a heterogeneous platform issue. In fact if the sync is SQL to SQL it is faster in Win 7 not slower.
If you would like any of the results of our testing to see if you can spot the issue, you would be welcome.
Guy
Edited by: 925129 on 16-Apr-2012 05:40
Edited by: 925129 on 16-Apr-2012 05:41

Cannot get data of the row from OLE DB provider "OraOLEDB.Oracle" for linked server

I have created a stored procedure in SQL Server for a report that uses parameters. In the report I am linking an Oracle table. I use a subquery like this to query the Oracle table: (select * from openquery(oracle_linked_server, 'select
partno, description from oracletable')). If I run the subquery it works fine every time. The linked server uses an oracle account which has access to the oracle table. When I first created the Stored Procedure it worked fine for me. When
I test the report, it worked fine. Then I asked another user to test it and it broke with the below error message.
OLE DB provider "OraOLEDB.Oracle" for linked server "XXXX_ORACLE" returned message "ORA-01403: no data found".
Msg 7346, Level 16, State 2, Procedure usp_report_XXXXXX, Line 15
Cannot get the data of the row from the OLE DB provider "OraOLEDB.Oracle" for linked server "XXXX_ORACLE".
Now when I try the report or the stored procedure, I get the same error. I tested the oracle subquery in the stored procedure and it still works. The report uses a service account to execute the stored procedure.
I am using SQL Server 2012 Developer Edition 64 bit (11.0.5058) Management Studio to develop the stored procedure. The SQL Server I am accessing and running the stored procedure is SQL Server 2008R2 Developer Edition 64bit (10.50.2550). The user
that tested the report for me has SQL Server 2008R2 but that shouldn't matter since he is running the report in Internet Explorer.
What is changing that it works for a while and then stops?
Fred
Fred Schmid

I found the answer. It was in the query. I put the TRIM statement on the part# field in the Oracle subquery and took the LTRIM function out of the ON clause that joined my SQL Server table with the Oracle linked server table. Now everything
works. The query looks like this:
SQL_Server_Table sst
LEFT OUTER JOIN
(SELECT * FROM OPENQUERY(OracleLinkedServer, 'SELECT TRIM(partNo) AS partNo, partDesc FROM OracleTable')) ols
ON sst.partNo = ols.partNo
Thanks for pointing me in the right direction.
Fred Schmid

Adding a table to a linked server in SQL

Hi
I have a linked server in SQL server management studio.
It has a list of oracle tables that can be reached through it. To add tables to the list do i need set up some permissions on the Oracle side?
thanks a lot for any help

To add to what Sunny posted. If the linked server uses a fixed user/password to connect to Oracle then in the Oracle database all you need do is get the required object privileges granted to the Oracle username being used in the linked server to Oracle. The grant can be direct to the username or to a role the username has been granted.
If the MS SQL Server Linked Server to Oracle does not use a fixed user then the SQL Server usernames have to also exist in Oracle or have been mapped via the linked server definition to an Oracle username. Different SQL Server users can have different Oracle usernames associated to them via the linked server definition so you may need the Oracle grants issued to one or more Oracle usernames.
Most linked servers use fixed users to connect to Oracle but you need to be aware this is not always true and when it is not true the list of tables shown under the linked server can vary based on the SQL Server user logged in.
HTH -- Mark D Powell --

Problem "The OLE DB provider for linked server reported an error. The provider reported an unexpected catastrophic failure Cannot fetch a row from OLE DB provider for linked server"

hi
i'd like to ask question about linked server.
my linked server used to work but now when i try to select from linked server i was told "The OLE DB provider for linked server reported an error. The provider reported an unexpected catastrophic failure Cannot fetch a row from OLE DB provider
for linked server"
but in fact for test connection i was told "the test connection to the linked server succeeded".
could anyone help me? thank u very much
best regards
martin

Hi,
In addition to Tracy's post we have to know those answers as well:
* what provider are you using for the connection
* what do you connect to
for example, if someone try to connect to oracle using sql server provider then several simple queries are going to work probably OK, but once you are trying to use T-SQL or any complex SQL query then the errors are starting.
please post the connection string (without the password!) + the query that you are trying to use.
[Personal Site] [Blog] [Facebook]

Linked server error 7303

Good morning,
I created a linked server to
access sql server 2008.
At first everything worked properly,
now returns the error 7303.
I have already shared the folder with all
of the database permits users full control
of sql server users , users of
the system, etc..
Does anyone know how can you fix?
I found a solution on the Internet,
says to create an Admin user
on the machine, and as a path
to a temporary folder on your
hard disk different from the profile, by entering
the required permissions to SQL Server, but not
seems to work after a while let us start, however,
to return the error 7303.
i found if i drop linked server , restart pc and reacreate it , it work , but when i restard pc all return error 7303.
SQL Version : 10.0.2573
Thanking you in advance,
GR

Hi Normand!,
Access db its a 97 version converted into 2000.
If i run a select statement(select * from TEST...TAB_EAN from SSMS error is(italian version):
Il provider OLE DB "Microsoft.Jet.OLEDB.4.0" per il server collegato "TEST" ha restituito il messaggio "Errore non specificato.".
Messaggio 7303, livello 16, stato 1, riga 1
Impossibile inizializzare l'oggetto origine dei dati del provider OLE DB "Microsoft.Jet.OLEDB.4.0" per il server collegato "TEST".
I've read the link you provide but without success.
The linked server use the provider: Microsoft.Jet.OLEDB.4.0
GR
update:
I tryed to use sql server with user Local System , i can create the linked server and use it, but if i restart the pc and restart the sql server service, i have the the same error (7303)

Linked server using ASEOLEDB

Similar Messages

Maybe you are looking for