Link server very slow

I created a link server to 'oracle', properties is below
Server Type : Microsoft OLE DB Provider for Oracle
Product name : ora
Data Source : sapdbproduction
Provider string : MSDAORA
Compare query response time (1 record)
PL-SQL : 0.5 sec
SQL Query Analyzer : 1.4 minute
How can i do?
Thanks in adv.
Hi
Post the DDL and DML.
Regards
Mike
"teera" wrote:

> I created a link server to 'oracle', properties is below
> Server Type : Microsoft OLE DB Provider for Oracle
> Product name : ora
> Data Source : sapdbproduction
> Provider string : MSDAORA
> Compare query response time (1 record)
> PL-SQL : 0.5 sec
> SQL Query Analyzer : 1.4 minute
> How can i do?
> Thanks in adv.
>
>
|||Mike
What is DDL and DML? Please explain me more?
Thanks
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:68EECFB8-4739-4277-A78A-A21F3F6CA33B@.microsoft.com...[vbcol=seagreen]
> Hi
> Post the DDL and DML.
> Regards
> Mike
> "teera" wrote:
|||DDL = Data Definition Language. It's basically the schema of the
associated DB objects (table(s), index(es), view(s), trigger(s), etc.).
DML = Data Manipulation Language. It's the queries that you're running
against those DB objects (SELECT, INSERT, UPDATE, DELETE). The queries
about which you say the response time through the linked server is slow.
Basically, nobody can help you if you don't give any details about the
problem. To help we'll need to see things like execution plans,
indexing of search arguments, etc. We can't do that if we don't know
what your schema looks like and what query you're trying to execute
against that schema. It's possible that the entire table data is being
sent from the Oracle box to the SQL box (through the linked server) and
then any WHERE clause is being applied (which would explain the slow
performance through the link but not direct to Oracle) but we can't tell
if you don't show us the schema & queries involved.
Cheers,
Mike.
teera wrote:
> Mike
> What is DDL and DML? Please explain me more?
> Thanks
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:68EECFB8-4739-4277-A78A-A21F3F6CA33B@.microsoft.com...
>
>
C

Link server very slow

I created a link server to 'oracle', properties is below
Server Type : Microsoft OLE DB Provider for Oracle
Product name : ora
Data Source : sapdbproduction
Provider string : MSDAORA
Compare query response time (1 record)
PL-SQL : 0.5 sec
SQL Query Analyzer : 1.4 minute
How can i do?
Thanks in adv.Hi
Post the DDL and DML.
Regards
Mike
"teera" wrote:

> I created a link server to 'oracle', properties is below
> Server Type : Microsoft OLE DB Provider for Oracle
> Product name : ora
> Data Source : sapdbproduction
> Provider string : MSDAORA
> Compare query response time (1 record)
> PL-SQL : 0.5 sec
> SQL Query Analyzer : 1.4 minute
> How can i do?
> Thanks in adv.
>
>|||Mike
What is DDL and DML? Please explain me more?
Thanks
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:68EECFB8-4739-4277-A78A-A21F3F6CA33B@.microsoft.com...[vbcol=seagreen]
> Hi
> Post the DDL and DML.
> Regards
> Mike
> "teera" wrote:
>|||DDL = Data Definition Language. It's basically the schema of the
associated DB objects (table(s), index(es), view(s), trigger(s), etc.).
DML = Data Manipulation Language. It's the queries that you're running
against those DB objects (SELECT, INSERT, UPDATE, DELETE). The queries
about which you say the response time through the linked server is slow.
Basically, nobody can help you if you don't give any details about the
problem. To help we'll need to see things like execution plans,
indexing of search arguments, etc. We can't do that if we don't know
what your schema looks like and what query you're trying to execute
against that schema. It's possible that the entire table data is being
sent from the Oracle box to the SQL box (through the linked server) and
then any WHERE clause is being applied (which would explain the slow
performance through the link but not direct to Oracle) but we can't tell
if you don't show us the schema & queries involved.
Cheers,
Mike.
teera wrote:
> Mike
> What is DDL and DML? Please explain me more?
> Thanks
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:68EECFB8-4739-4277-A78A-A21F3F6CA33B@.microsoft.com...
>
>
>
C

Link server very slow

I created a link server to 'oracle', properties is below
Server Type : Microsoft OLE DB Provider for Oracle
Product name : ora
Data Source : sapdbproduction
Provider string : MSDAORA
Compare query response time (1 record)
PL-SQL : 0.5 sec
SQL Query Analyzer : 1.4 minute
How can i do?
Thanks in adv.Hi
Post the DDL and DML.
Regards
Mike
"teera" wrote:
> I created a link server to 'oracle', properties is below
> Server Type : Microsoft OLE DB Provider for Oracle
> Product name : ora
> Data Source : sapdbproduction
> Provider string : MSDAORA
> Compare query response time (1 record)
> PL-SQL : 0.5 sec
> SQL Query Analyzer : 1.4 minute
> How can i do?
> Thanks in adv.
>
>|||Mike
What is DDL and DML? Please explain me more?
Thanks
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:68EECFB8-4739-4277-A78A-A21F3F6CA33B@.microsoft.com...
> Hi
> Post the DDL and DML.
> Regards
> Mike
> "teera" wrote:
>> I created a link server to 'oracle', properties is below
>> Server Type : Microsoft OLE DB Provider for Oracle
>> Product name : ora
>> Data Source : sapdbproduction
>> Provider string : MSDAORA
>> Compare query response time (1 record)
>> PL-SQL : 0.5 sec
>> SQL Query Analyzer : 1.4 minute
>> How can i do?
>> Thanks in adv.
>>|||DDL = Data Definition Language. It's basically the schema of the
associated DB objects (table(s), index(es), view(s), trigger(s), etc.).
DML = Data Manipulation Language. It's the queries that you're running
against those DB objects (SELECT, INSERT, UPDATE, DELETE). The queries
about which you say the response time through the linked server is slow.
Basically, nobody can help you if you don't give any details about the
problem. To help we'll need to see things like execution plans,
indexing of search arguments, etc. We can't do that if we don't know
what your schema looks like and what query you're trying to execute
against that schema. It's possible that the entire table data is being
sent from the Oracle box to the SQL box (through the linked server) and
then any WHERE clause is being applied (which would explain the slow
performance through the link but not direct to Oracle) but we can't tell
if you don't show us the schema & queries involved.
Cheers,
Mike.
teera wrote:
> Mike
> What is DDL and DML? Please explain me more?
> Thanks
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:68EECFB8-4739-4277-A78A-A21F3F6CA33B@.microsoft.com...
>>Hi
>>Post the DDL and DML.
>>Regards
>>Mike
>>"teera" wrote:
>>
>>I created a link server to 'oracle', properties is below
>> Server Type : Microsoft OLE DB Provider for Oracle
>> Product name : ora
>> Data Source : sapdbproduction
>> Provider string : MSDAORA
>>Compare query response time (1 record)
>> PL-SQL : 0.5 sec
>> SQL Query Analyzer : 1.4 minute
>>How can i do?
>>Thanks in adv.
>>
>
>
--
ÿþC

Link server problrm connecting to Oracle

I get the following error after trying to do update to an Oracle 9i table
from SQL Server 2000. :
The operation could not be performed because the OLE DB provider 'MSDAORA'
was unable to begin a distributed transaction.
Any ideas to solve this?
Check the following article:
INF: Troubleshooting Linked Server Error 7391
http://support.microsoft.com/?id=306212
-Sue
On Wed, 23 Mar 2005 12:44:06 GMT, "Mori"
<obibiman.nospam@.yahoo.com> wrote:

>I get the following error after trying to do update to an Oracle 9i table
>from SQL Server 2000. :
>The operation could not be performed because the OLE DB provider 'MSDAORA'
>was unable to begin a distributed transaction.
>Any ideas to solve this?
>

Link server problrm connecting to Oracle

I get the following error after trying to do update to an Oracle 9i table
from SQL Server 2000. :
The operation could not be performed because the OLE DB provider 'MSDAORA'
was unable to begin a distributed transaction.
Any ideas to solve this?Check the following article:
INF: Troubleshooting Linked Server Error 7391
http://support.microsoft.com/?id=306212
-Sue
On Wed, 23 Mar 2005 12:44:06 GMT, "Mori"
<obibiman.nospam@.yahoo.com> wrote:

>I get the following error after trying to do update to an Oracle 9i table
>from SQL Server 2000. :
>The operation could not be performed because the OLE DB provider 'MSDAORA'
>was unable to begin a distributed transaction.
>Any ideas to solve this?
>sql

Link Server error: Msg 7399

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: [IBM][Client Access Express ODBC Driver (32-bit)]Driver not capable.]
What to do ? What to do ??Well , this Error belongs to Distributed Queries Error Messages collection.

- Remote OLE DB Data Source : ODBC Data Source
- OLE DB Provider : Microsoft OLE DB Provider for ODBC
- Provider Name : MSDASQL

The problem you are getting with only receiving one row on a select statement can be fixed by going into the configuration of the Client Access DSN and go to the other tab and check always scrollable, this will get all the rows.

As far as the other issue getting the error
Server: Msg 7399, Level 16, State 1, Line 1 OLE DB provider 'MSDASQL' reported an error. [OLE/DB provider returned message: [IBM][Client Access Express ODBC Driver (32-bit)]Driver not capable.]

You get this when journaling is not turned on the table on the AS400. Have one of your AS400 people turn journaling on for all the tables you need to access.

Since you noted that ..." [IBM][Client Access Express ODBC Driver (32-bit)]Driver not capable.] ".... I just could compare this error with one more familiar to Microsoft platform, and what are the reasons for getting this Error when trying to connect to MS Access DB.

1. MS Access DB is not secured Db , and there is no login : Admin with No Password .

2. The Access database is secured and :HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Sys temDB registry key is not pointing to the correct Access workgroup file.

-If you are trying to Change Data , try without : BEGIN >> COMMIT block, if possible.

-also try this link :

http://www.iseries.ibm.com/developer/db2/documents/mts/mts5.html

Hope this is something to start solving your problem.

rgds.
srdjan|||I linked two MSSQL 2000 servers by using enterprise manager. I succeeded in connecting between server 1(local) and server2 (remote). I have another remote one--server3. I used the same method to try connecting either local and server3, or server2 and server3.

I can do on local and server2 to see data from server3--

select * from server3.pubs.dbo.authors

however if I try to do this on server3

select * from server2.pubs.dbo.authors

I got following error messages:

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error. The provider did not give any information about the error.

So what is the problem here?

I will appreciate greatly for your help.

Cathy|||1. Check list of Linked Servers in SYSSERVERS system table ( you should have both (Server2 and Server3 ) servers listed .
2. Verify that there is a login mapping for the current user on Server3.
3. Check the rights of user you are trying to connect from your Server to Server3 . ( at least you must SELECT rights on table you are querying) ....

--Returns the list of linked servers defined in the local server
exec sp_linkedservers

--Creates a linked server
exec sp_addlinkedserver

hope this help

rgds.
srdjan|||Thanks for reply.

I checked all . I also used

CREATE Database NorthwindnDistributed
Go

Use NorthwindnDistributed
CREATE TABLE dbo.Customers
(CustomerID char(5),
CompanyName nvarchar(40))
EXEC sp_addlinkedserver @.server = 'remoteserver',
@.srvproduct ='SQLServer OLEDB Provider',
@.provider ='SQLOLEDB',
@.datasrc = 'remote server IPaddress'

IF not Exists (select 'True' From master.dbo.syslogins where Name = 'remoteUser')
EXEC sp_addlogin 'remoteUser','remotePassword'

Use NorthwindnDistributed
exec sp_adduser 'remoteUser'
exec sp_addrolemember 'db_owner', 'remoteUser'
exec sp_addlinkedsrvlogin @.rmtsrvname = GM,
@.useself = FALSE,
@.rmtuser = 'remoteUser',
@.rmtpassword ='remotePassword'

exec sp_serveroption @.server = GM,
@.OPTNAME ='lazy schema validation',
@.OPTVALUE = 'TRUE'

to create new linked servers from both of local and remote sides. It still give me the error message like

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error. The provider did not give any information about the error.

I can do "select ..." from one side of server. But when I changed to other servers, I don't have any problems to connect them and work on them. If there is anything wrong when this server is set up? Why can I not get any error messages when i do the same operation on other servers but only fail on one particular server?:confused:

Thanks for any reply.

HELP!

Link Server between Oracle and SQL Server error

This message appears :
"Error 7399: OLE DB provider 'MSDAORA' reported an error. OLE DB error trace
[OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ]."
My server is a Windows 2000 Server SP4, with SQLServer Enterprise SP3a.
Oracle client 7.3.3.5.0 had been installed. When I use SQL Plus 3.3 (Little
tool installed with Oracle client) it connects correcty to Oracle Database.
Unfortunatelly, when I want create a "linked server" and I click on "tables"
this message appears !?
Who can help me ?
Oracle doesn't support 7.x anymore, or 8x for that matter. Are you sure
you're running 7.x?
"Olivier TACKELS" wrote:

> This message appears :
> "Error 7399: OLE DB provider 'MSDAORA' reported an error. OLE DB error trace
> [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ]."
> My server is a Windows 2000 Server SP4, with SQLServer Enterprise SP3a.
> Oracle client 7.3.3.5.0 had been installed. When I use SQL Plus 3.3 (Little
> tool installed with Oracle client) it connects correcty to Oracle Database.
> Unfortunatelly, when I want create a "linked server" and I click on "tables"
> this message appears !?
> Who can help me ?
>
|||You not only have an Oracle issue, there is also an MDAC issue. I have seen
that and similar issues when upgrading from MDAC 2.2-5 to MDAC2.6-7.
MS's Oracle drivers and interfaces are based on Oracle 8.1.7.6 from MDAC 2.5
on. Your client MDAC needs to be in sync with your db server mdacs.
Joseph R.P. Maloney, CSP,CCP,CDP
"fnguy" wrote:
[vbcol=seagreen]
> Oracle doesn't support 7.x anymore, or 8x for that matter. Are you sure
> you're running 7.x?
> "Olivier TACKELS" wrote:
|||Additional thought:
What release is your Oracle database? The 10g ones won't even talk to
Oracle 7x (or 8.0.x). If your Oracle is 10g, then you definitely need to
look at MDAC and SQL*NET.
Joseph R.P. Maloney, CSP,CCP,CDP
"fnguy" wrote:
[vbcol=seagreen]
> Oracle doesn't support 7.x anymore, or 8x for that matter. Are you sure
> you're running 7.x?
> "Olivier TACKELS" wrote:

Link Server between Oracle and SQL Server error

This message appears :
"Error 7399: OLE DB provider 'MSDAORA' reported an error. OLE DB error trace
[OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005
: ]."
My server is a Windows 2000 Server SP4, with SQLServer Enterprise SP3a.
Oracle client 7.3.3.5.0 had been installed. When I use SQL Plus 3.3 (Little
tool installed with Oracle client) it connects correcty to Oracle Database.
Unfortunatelly, when I want create a "linked server" and I click on "tables"
this message appears !?
Who can help me ?Oracle doesn't support 7.x anymore, or 8x for that matter. Are you sure
you're running 7.x?
"Olivier TACKELS" wrote:

> This message appears :
> "Error 7399: OLE DB provider 'MSDAORA' reported an error. OLE DB error tra
ce
> [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x800040
05: ]."
> My server is a Windows 2000 Server SP4, with SQLServer Enterprise SP3a.
> Oracle client 7.3.3.5.0 had been installed. When I use SQL Plus 3.3 (Littl
e
> tool installed with Oracle client) it connects correcty to Oracle Database
.
> Unfortunatelly, when I want create a "linked server" and I click on "table
s"
> this message appears !?
> Who can help me ?
>|||You not only have an Oracle issue, there is also an MDAC issue. I have seen
that and similar issues when upgrading from MDAC 2.2-5 to MDAC2.6-7.
MS's Oracle drivers and interfaces are based on Oracle 8.1.7.6 from MDAC 2.5
on. Your client MDAC needs to be in sync with your db server mdacs.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"fnguy" wrote:
[vbcol=seagreen]
> Oracle doesn't support 7.x anymore, or 8x for that matter. Are you sure
> you're running 7.x?
> "Olivier TACKELS" wrote:
>|||Additional thought:
What release is your Oracle database? The 10g ones won't even talk to
Oracle 7x (or 8.0.x). If your Oracle is 10g, then you definitely need to
look at MDAC and SQL*NET.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"fnguy" wrote:
[vbcol=seagreen]
> Oracle doesn't support 7.x anymore, or 8x for that matter. Are you sure
> you're running 7.x?
> "Olivier TACKELS" wrote:
>

Link Server between Oracle and SQL Server error

This message appears :
"Error 7399: OLE DB provider 'MSDAORA' reported an error. OLE DB error trace
[OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ]."
My server is a Windows 2000 Server SP4, with SQLServer Enterprise SP3a.
Oracle client 7.3.3.5.0 had been installed. When I use SQL Plus 3.3 (Little
tool installed with Oracle client) it connects correcty to Oracle Database.
Unfortunatelly, when I want create a "linked server" and I click on "tables"
this message appears !?
Who can help me ?Oracle doesn't support 7.x anymore, or 8x for that matter. Are you sure
you're running 7.x?
"Olivier TACKELS" wrote:
> This message appears :
> "Error 7399: OLE DB provider 'MSDAORA' reported an error. OLE DB error trace
> [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ]."
> My server is a Windows 2000 Server SP4, with SQLServer Enterprise SP3a.
> Oracle client 7.3.3.5.0 had been installed. When I use SQL Plus 3.3 (Little
> tool installed with Oracle client) it connects correcty to Oracle Database.
> Unfortunatelly, when I want create a "linked server" and I click on "tables"
> this message appears !?
> Who can help me ?
>|||You not only have an Oracle issue, there is also an MDAC issue. I have seen
that and similar issues when upgrading from MDAC 2.2-5 to MDAC2.6-7.
MS's Oracle drivers and interfaces are based on Oracle 8.1.7.6 from MDAC 2.5
on. Your client MDAC needs to be in sync with your db server mdacs.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"fnguy" wrote:
> Oracle doesn't support 7.x anymore, or 8x for that matter. Are you sure
> you're running 7.x?
> "Olivier TACKELS" wrote:
> > This message appears :
> > "Error 7399: OLE DB provider 'MSDAORA' reported an error. OLE DB error trace
> > [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ]."
> >
> > My server is a Windows 2000 Server SP4, with SQLServer Enterprise SP3a.
> > Oracle client 7.3.3.5.0 had been installed. When I use SQL Plus 3.3 (Little
> > tool installed with Oracle client) it connects correcty to Oracle Database.
> > Unfortunatelly, when I want create a "linked server" and I click on "tables"
> > this message appears !?
> >
> > Who can help me ?
> >
> >|||Additional thought:
What release is your Oracle database? The 10g ones won't even talk to
Oracle 7x (or 8.0.x). If your Oracle is 10g, then you definitely need to
look at MDAC and SQL*NET.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"fnguy" wrote:
> Oracle doesn't support 7.x anymore, or 8x for that matter. Are you sure
> you're running 7.x?
> "Olivier TACKELS" wrote:
> > This message appears :
> > "Error 7399: OLE DB provider 'MSDAORA' reported an error. OLE DB error trace
> > [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ]."
> >
> > My server is a Windows 2000 Server SP4, with SQLServer Enterprise SP3a.
> > Oracle client 7.3.3.5.0 had been installed. When I use SQL Plus 3.3 (Little
> > tool installed with Oracle client) it connects correcty to Oracle Database.
> > Unfortunatelly, when I want create a "linked server" and I click on "tables"
> > this message appears !?
> >
> > Who can help me ?
> >
> >

link from sql2005 (64-bit) to sql 7 (32-bit).

Hi: I'm trying to link from sql2005 (64-bit) SP1 to sql 7 (32-bit) SP4.
I get the following error:
OLE DB provider "SQLNCLI" for linked server "sql7" returned message
"Unspecified error".
OLE DB provider "SQLNCLI" for linked server "sql7" returned message "The
stored procedure required to complete this operation could not be found on
the server. Please contact your system administrator.".
Msg 7311, Level 16, State 2, Line 1
Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider
"SQLNCLI" for linked server "sql7". The provider supports the interface, but
returns a failure code when it is used.
How can I get these servers linked?
Regards,I just ran into a similar problem, but from 64 bit SQL 2005 trying to link
to 32 bit SQL 2000. What I did on the 2000 server was run the instcat.sql
from the latest service pack installation I did on the 2000 server. In my
case it was SP3a. There are instructions to change the last insert statement
to the table to reflect the version of SQL Server (select @.@.version) that
you are running. In my case it was .977. That fixed my problems.
Jackie
"José" <josedc@.starmedia.com> wrote in message
news:OE2iT1GlGHA.3720@.TK2MSFTNGP03.phx.gbl...
> Hi: I'm trying to link from sql2005 (64-bit) SP1 to sql 7 (32-bit) SP4.
> I get the following error:
> OLE DB provider "SQLNCLI" for linked server "sql7" returned message
> "Unspecified error".
> OLE DB provider "SQLNCLI" for linked server "sql7" returned message "The
> stored procedure required to complete this operation could not be found on
> the server. Please contact your system administrator.".
> Msg 7311, Level 16, State 2, Line 1
> Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider
> "SQLNCLI" for linked server "sql7". The provider supports the interface,
> but
> returns a failure code when it is used.
> How can I get these servers linked?
> Regards,
>sql