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

Similar Messages

Instant client 10.2.0.3 used with ms sql linked server doesn't work

Hi,
instant client version 10.2.0.3 doesn't work as microsoft sql linked server (both 2000, 2005) while 10.2.0.1 does. (tested by overwriting files in instant client directory - basic instalation, then restart mssql services) - the message is, that the oracle client is not installed when running sql (registration of linked server is ok).
Is it a known issue or is there any workaround?
(Windows XP, 2003, MS SQL 2005, MS SQL 2000, Oracle 9.2.0.6)
Thanks,
Pavel

I installed oracle-instantclient-basic-10.2.0.3-1.i386.rpm on a redhat box to
connect oracle database server 9.2.0.8.0 install on win box.Is there any other Oracle software installed on the RedHat machine?
In which directory did you install Instant Client?
Can you login with sqlplus?
On the database server, I defined parameters like this :
NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS'
NLS_NUMERIC_CHARACTERS='. 'This will have no effect on your problem - these are client environment variables.
Before starting apache (lampp) I set Oracle environement like this :
export NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS'
export NLS_NUMERIC_CHARACTERS='. '
My application worked very fine.
BUT a few days ago (1 week), in my application, the date format display wrong,
I have this format : DD/MON/YYYY even with
export NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS'
before starting apache.The ancient question: Do you remember what you changed before it stopped working?
So I stop my apache and try set Oracle environment like this :
export ORACLE_HOME=/usr/lib/oracle/10.2.0.3/clientAs has been said, do away with that.
export PATH=$ORACLE_HOME/bin:$PATHYou don't need that either.
Except is might be nice to have the directory that contains sqlplus in PATH.
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATHNow that surprises me.
Normally, instant client shared libraries are not installed in a subdirectory.
Does this "lib" directory exist?
You should add the directory containing the *.so files to LD_LIBRARY_PATH.
When I restart apache and test my application, an error php message occurs :
Ocisessionbegin error while trying TO retrieve text FOR error ora-12705
I check my oracle_home, I don't think I make a mistake?It seems that Oracle cannot find the instant client shared library libociei.so.
This library must be found in LD_LIBRARY_PATH.
In this context it would be interesting to know (as I asked above) if any other Oracle products are installed on this machine.
Yours,
Laurenz Albe

Can ODBC set by Instant Client be used in MS SQL linked Server?

Hi:
I want to know if a ODBC set by Instant Client can be used to set a linked server in MS SQL.
I follow the install instruction about Instant Client.
I create a ODBC setting and the connection tested successful.
I also build it in DTS package in MS SQL and the data transfer process can be run correctly.
But when I tried to build a linked server from MS SQL to oracle, it always returned the error message
System1 Setting:
MS Win 2003 + MS SQL 2000 + Instant Client 10.1.0.4
System2 Setting:
MS Win 2000 + Oracle 9.2
Any opinion or suggestion is appreciated.
Toni Lee

with t_segment
as
     select block_id, blocks, owner, segment_name,segment_type
       from dba_extents
      where tablespace_name = upper('&1')
      union all
     select block_id, blocks, 'sys' owner, 'Free' segment_name, 'FREE'
       from dba_free_space
      where tablespace_name = upper('&1')
      order by 1
t_segment_1
as
      select block_id,
          blocks,
          owner, segment_name, segment_type,
          owner||'-'||segment_name||'-'||segment_type seg
        from t_segment t
       order by 1
select block_id, owner, segment_name, segment_type, sum(blocks) blocks
   from (select val block_id, owner, segment_name, segment_type, blocks
        from (select block_id,
               blocks,
                        owner, segment_name, segment_type,
               seg,
               row_number() over(order by block_id) rno,
               nvl(lag(seg) over(order by block_id),' ') lag_seg
             from t_segment_1)
       model
       return updated rows
       dimension by(rno)
       measures(block_id, blocks, seg, lag_seg, 0 val, owner, segment_name, segment_type)
       rules update
          val[any] = case when seg[cv()] <> lag_seg[cv()] then block_id[cv()] else val[cv()-1] end
group by block_id, owner, segment_name, segment_type
order by block_id

LabView 2010 application runs twice as slow in Windows 7

When our company mandated the replacement of Windows XP PC's, my LabView test application that was compiled in LabView 2010 runs over twice as slow on a Fujitsu Esprimo E710E86+ machine. The application uses a GPIB USB - HS adapter to control an HP 4285 Impedance analyzer whose signals are switched to it using two (2) SCXI chassis that contains five (5) SCXI-1193 switch modules. This chassis uses the USB-1359 communicator.
On the Windows XP machine that is being replaced (a Dell Optiplex 960), a typical set of measurements takes around 40 seconds to complete. The new Windows 7 machine takes about 100 seconds to do the same set of measurements. Has anyone noted this increase in test time???
Thank you.
Rod Johnson
Test Engineering
FujiFilm SonoSite Inc.

Hello Rod,
Before updating to LV 2013 I'd recommend isolating what components are causing the slowdown or at least trying to eliminate some of the variables - right now there's a new PC, new OS, new physical connections, and perhaps even new hardware, so figuring out which of these is causing the slowdown should be the first order of business. I've seen issues simlar because USB devices were switched around to different (built-in) ports on the same machine.
A few things to check:
-What does this application do? Are you doing any intensive data manipulation or is this mostly a call-and-response type application?
-What does your system resource utilization look like on the two machines? In either case, are you using more or less RAM on one machine or railing one or more CPUs?
-Do you see the same sort of performance hit on a Windows 7 installation on an Optiplex or similar machine?
-Did you change drivers when you upgraded to Windows 7?
-What NI driver version(s) are/were you using?
-Does this application log data data to disk or perform any network operations?
-Have you attempted recompiling the 2010 executable on "new" hardware? The LabVIEW compiler will optimize for the platform it is being built on and it seems highly likely that the Dell and Fujitsu machines have different processors. As a note I've never seen recompiling in this fashion result in a 100%+ speedup.
-Have you taken a look at the machine's I/O traces to see how long the acquisition itself takes?
-Have you tried moving the USB connections to different ports? Most desktop PCs nowadays have one hub on the front and one on the back of the machine, although I'm not familiar with Fujitsu desktops. If the adapters you are using or anything else on the machine is forcing a USB 2.0/3.0 port to 1.0 or something this could be a factor.
Regards,
Tom L.

User created SQL Agent Job that uses linked server with Windows authentication

OK, here's what I want to do, but not sure exactly what I need to accomplish it.
Environment
Windows 2008 Enterprise
SQL 2012 Enterprise
SQL Server & SQL Agent running under AD account (which has local Windows Administrative privileges...yes, I know..bad!)
Linked server to Teradata utilizing AD account mappings (the linked server works successfully and each windows login is mapped to a Teradata LDAP login)
Requirement
Allow non sysadmins to create SQL Agent jobs which execute TSQL statements which use OPENQUERY(LDAPLinkedServer, '....) syntax
I've already given the non sysadmins the necessary permissions to create and run SQL Agent jobs, and I understand that the jobs run under their login context, but I suspect that I'm missing something when it comes to the linked server.
Each windows user could have access to different databases/tables on the Teradata system that even I (the SQL Server sysadmin) don't have access to.
How can I facilitate this functionality? Any ideas?

I think I may have been over complicating the Teradata piece. The authentication methodology in Teradata is LDAP, which just means that it authenticates against AD, but you still have to submit your Windows login & password. It doesn't automatically
authenticate you just because you're logged into Windows.
The linked server has the mapping for the individual windows logins like:
Local Login = <domain>.<windows id>
Remote User = <windows id>
Remote Password = <windows password>
This setup requires the user to have to change the passwords in the linked server whenever they change their passwords according to domain policy (every xx days)...but we've created a utility proc that they can use to do this.
So, I'm thinking that Teradata isn't really part of this equation.

Linked Server SQL 2008 64 bit Windows Server 2008 64 bit

Hello there,
I'm trying to access my customers Oracle database with a SQL Linked Server. The error I get is:
Cannot create an instance of OLE DB provider "OraOLEDB.Oracle" for linked server...
I did the following steps:
1. Installed Oracle client 10g with a custom installation and selected everything.
2. Created a tnsnames.ora
dev =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dijkora01)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = dev)
3. Tested this with tnsping dev, which said that the connection is OK.
4. Activated 'Allow inprocess' for my OraOLEDB.Oracle provider for the linked servers in my SQL Server Management Studio.
5. Created a new linked server with:
Linked Server: IAP
Provider: Oracle Provider for OLE DB
Product name: Oracle
Data source: dev
In the security tab I activated 'Be made using this security context'. When I now press 'OK' I get the above error message.
Can someone help me with this?

Windows 7 Enterprise 32-Bit
Installed the version 12 for 32 bit ODAC and it worked. The key is to Install as Administrator once it is unzipped.
Was able to set up Listener then
Was able to set up ODBC using the ODAC. Connect MS Access 2010 to the Oracle views.
Then, tried to install the 64 Bit onto Windows 2008 Server.
It locked up during installation both times.
Installed ODAC without an error.
However, the ODBC setup will not provide a list of the servers in the ODBC TNS Service Name listbox for Server 2008.
In Windows 7, it populates the TNS Service Name.
The list box in Windows 2008 is empty.
Do you know what would cause that?
The .ORA file scrips look the same on Windows 2008 as they do on Windows 7 except it does not have the (server = Dedicated) argument.
Thanks.

SQL 2000 LINKED SERVER ERROR 7303 WITH SQL 2012 ON WINDOWS SERVER 2012 R2

Hi all,
I have a problem with SQL Server 2012 and a linked server for SQL 2000 database.
System specification:
Windows server 2012 64 bit
SQL SERVER 2012 64 bit
REMOTE SERVER SQL 2000 32 bit
I've installed sql native client 32bit,create a SYSTEM DSN odbc connection with "SQL Server" driver named "MYSERVER".
Create a linked server with the query below in SQL 2012:
EXEC master.dbo.sp_addlinkedserver @server =N'MYSERVER', @srvproduct=N'MYSERVER', @provider=N'MSDASQL', @datasrc =N'MYSERVER', @location=N'System';
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'MySERVER',@useself=N'True',@locallogin=NULL,@rmtuser=NULL,@rmtpassword=NULL
GO
but when i browse the linked server i receved error 7303.

You need 64-bit MSDASQL. It is the bitness of the server you are connecting from that matters. 64-bit executables cannot hook into 32-bit DLL.
However, I suspect that you will not get things to work anyway. At least I have not seen anyone this far who has been able to set up a linked server from SQL 2012 to SQL 2000. I know that when I tried this, the following providers had this result:
SQLNCLI11 - does not support connections to SQL 2000.
SQLNCLI10 - failed with some obscure message that I don't recall.
SQLNCLI - Don't recall that the problem was here.
SQLOLEDB - SQLOLEDB is always replaced with the most recent version of SQLNCLI, so this fails because of lack of support.
I don't think I got through all version of the ODBC drivers, though.
Erland Sommarskog, SQL Server MVP, [email protected]

Permissions needed for sql server job to execute stored procedure on linked server?

Hi all
I have a job step which attempts to call a stored procedure on a linked server.
This step is failing with a permission denied error. How can I debug or resolve this?
The job owner is sysadmin on both servers so should have execute permission to the database/proc I'm calling, right?
The error is:
The EXECUTE permission was denied on the object 'myProc', database 'myDatabase', schema 'dbo'. [SQLSTATE 42000] (Error 229). The step failed.
My code is:
EXEC [LinkedServer].myDatabase.dbo.myProc
Also tried:
SELECT * FROM OPENQUERY([LinkedServer], 'SET FMTONLY OFF EXEC myDatabase.dbo.myProc')
With the same result.
Any help appreciated.

The job owner may be sysadmin on the remote server. The service account for SQL Server Agent may not. And it is the latter that counts, since the it the service accounts that logs in and impersonates the job owner. But the impersonation inside SQL Server
does not count much in Windows, and it is through Windows connection is made to the other site.
One way to resolve this is to set up a login mapping for the job owner. The login mapping must be for an SQL login on the remote server.
You can verify the theory, but running this query from the job:
SELECT * FROM OPENQUERY([LinkedServer], 'SELECT SYSTEM_USER')
By the way, putting SET FMTONLY OFF in OPENQUERY is a terrible idea. This has the effect that the procedure is executed twice. (Unless both servers are SQL 2012 or higher in which case FMTONLY has no effect at all.)
Erland Sommarskog, SQL Server MVP, [email protected]

Errro while installing sql server 2012 express edition on Windows 8 -64 version

Hi,
Im trying to install sql server 2012 express edition on windows 8 machine(64 bit),however im getting same error every time.
The following error has occurred:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337
i've googled and checked all prerequisite which is already installed.so not finding the reason behind this error.
it would be great if any one can help on resolving this error.
Thanks in advance
Regards
Ritesh

Hi ,
Thanks for help. here is the log summary text
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2068051679
Start time:                    2014-02-05 12:30:44
End time:                      2014-02-05 12:36:21
Requested action:              Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name:                  IDEA-PC
Machine processor count:       4
OS version:                    Future Windows Version
OS service pack:
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services
1033                 Developer Edition    10.50.1600.1    No
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         SQL Server Replication
1033                 Developer Edition    10.50.1600.1    No
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text and Semantic Extractions for Search 1033
Developer Edition    10.50.1600.1    No
SQL Server 2008 R2
Management Tools - Basic                 1033                 Developer Edition
10.50.1600.1    No
SQL Server 2008 R2
Management Tools - Complete              1033                 Developer Edition    10.50.1600.1
No
SQL Server 2008 R2
Client Tools Connectivity                1033                 Developer Edition    10.50.1600.1
No
SQL Server 2008 R2
Client Tools Backwards Compatibility     1033                 Developer Edition    10.50.1600.1    No
SQL Server 2008 R2
Client Tools SDK                         1033
Developer Edition    10.50.1600.1    No
SQL Server 2008 R2
Integration Services                     1033                 Developer Edition
10.50.1600.1    No
Package properties:
Description:                   Microsoft SQL Server 2012 Service Pack 1
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
SPLevel:                       0
Installation location:         c:\b33170cf028067db5b8335d2\x64\setup\
Installation edition:          Express
Product Update Status:
None discovered.
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      true
AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Disabled
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASLOGDIR:                      Log
ASPROVIDERMSOLAP:              1
ASSERVERMODE:                  MULTIDIMENSIONAL
ASSVCACCOUNT:                  <empty>
ASSVCPASSWORD:                 <empty>
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CLTCTLRNAME:                   <empty>
CLTRESULTDIR:                  <empty>
CLTSTARTUPTYPE:                0
CLTSVCACCOUNT:                 <empty>
CLTSVCPASSWORD:                <empty>
CLTWORKINGDIR:                 <empty>
COMMFABRICENCRYPTION:          0
COMMFABRICNETWORKLEVEL:        0
COMMFABRICPORT:                0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE:               0
CTLRSVCACCOUNT:                <empty>
CTLRSVCPASSWORD:               <empty>
CTLRUSERS:                     <empty>
ENABLERANU:                    true
ENU:                           true
ERRORREPORTING:                false
FEATURES:                      SQLENGINE, REPLICATION, SNAC_SDK
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 <empty>
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS:              false
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    SQLFASHION
INSTANCENAME:                  SQLFASHION
ISSVCACCOUNT:                  NT AUTHORITY\Network Service
ISSVCPASSWORD:                 <empty>
ISSVCSTARTUPTYPE:              Automatic
MATRIXCMBRICKCOMMPORT:         0
MATRIXCMSERVERNAME:            <empty>
MATRIXNAME:                    <empty>
NPENABLED:                     0
PID:                           *****
QUIET:                         false
QUIETSIMPLE:                   false
ROLE:                          AllFeatures_WithDefaults
RSINSTALLMODE:                 DefaultNativeMode
RSSHPINSTALLMODE:              DefaultSharePointMode
RSSVCACCOUNT:                  <empty>
RSSVCPASSWORD:                 <empty>
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  Latin1_General_CI_AI
SQLSVCACCOUNT:                 NT Service\MSSQL$SQLFASHION
SQLSVCPASSWORD:                <empty>
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           idea-pc\lenovo
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  false
TCPENABLED:                    0
UIMODE:                        AutoAdvance
UpdateEnabled:                 true
UpdateSource:                  MU
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Component name:                SQL Server Common Files
Component error code:          2337
Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\sql_common_core_Cpu64_1.log
Error description:             The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337.
Error help link:
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Component name:                SQL Server Common Files
Component error code:          2337
Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\sql_common_core_Cpu64_1.log
Error description:             The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337.
Error help link:
Feature:                       SQL Client Connectivity
Status:                        Passed
Feature:                       SQL Client Connectivity SDK
Status:                        Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\SystemConfigurationCheck_Report.htm

Connect Sql Server From Oracle Both on Windows

I want to connect my SQL Server running on Windows2003 with my oracle database 10g which is also on windows through some odbc which i have also created on my machine running oracle 10g. Can some one guide me with simple steps.

Generally most folks use OLEDB rather than ODBC for that.
If you have Metalink access, check out the following note:
Note.191368.1 Ext/Pub How to Create a Sql Server Linked Server With The Oracle Provider for OLE DB:
Hope it helps,
Greg

Distributed transaction using linked server not working in SQL Server 2008 64 bit

Hi. I have had an issue trying to get distributed transactions to work in SQL Server 2008 using a linked server. The error message I get is
OLE DB provider "SQLNCLI10" for linked server "pod1" returned message "No transaction is active.".
Msg 7391, Level 16, State 2, Line 3
The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "pod1" was unable to begin a distributed transaction.
My Environment:
Windows Server 2008 Enterprise 64 bit, SQL Server 2008 Enterprise 64 bit
Problem occurs with multiple different builds of SQL Server 2008 - I have been able to reproduce the problem with 10.0.1600.0, 10.0.1779.0 (CU 2), as well as 10.0.2531 (SP1)
I am aware that other people have had this issue and have reviewed all existing posts. I have verified that the MSDTC is configured correctly on both machines. I have also used DTCTester to verify that DTC is working correctly on all machines in question.
None of the mentioned resolutions has solved this problem for me.
I am not seeing this problem occur on my 32 bit test machines - it is only occurring if at least one of the two machines is 64 bit.

Hi All,
I realise that this topic may be a little bit out-of-date but if someone gets here from some search engine trying to find a solution for DTC problems, this MAY be useful.
So... I recently had the same issue, tried all the approaches described in KB and other articles, but it didn't help. Because my task to solve this was not of the highest priority I forgot about it for some time.
Today I was troubleshooting some other issue and, by accident discovered source of that first problem:
In the EventViewer I found Error entry logged by MSDTC saying:
"The local MS DTC detected that the MS DTC on vm-server1 (other machine name that also runs DTC - my comment) has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate
with each other. This problem typically occurs if one of the systems were cloned using unsupported cloning tools. MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install'
from the command prompt will fix the problem. Note: Running 'msdtc -uninstall' will result in the system losing all MS DTC configuration information."
So I followed suggestion and run:
msdtc -uninstall
msdtc -install
This solved my problems with DTC. Hope it will help someone.
Piotr

Importing Data from MS Access into SQL Serevr 2005 via Linked Server: User-Dependent failure

I am operating an Express version of SQL Server 2005 on a Windows XP machine.
I have successfully setup a linked server to a remote Access (.mdb) database. With my user account (Windows authentication) I can retrieve and store data without any problem.
I have another user (apparently with same settings as my own account) that is always failing to get the data.
The Error message he gets is:
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "TSU_Tmp" returned message "The Microsoft Jet database engine cannot open the file '\\DSITSO-NT0001\Exchange\Database5.mdb'. It is already opened exclusively by another
user, or you need permission to view its data.".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "TSU_Tmp".
Here below the code used to set up the linked server (coming from the Code Snippets of SQL Server 2005).
EXEC sp_addlinkedserver
@server = N'TSU_Tmp',
@provider = N'Microsoft.Jet.OLEDB.4.0',
@srvproduct = N'OLE DB Provider for Jet',
@datasrc = N'\\DSITSO-NT0001\Exchange\Database5.mdb'
EXEC sp_addlinkedsrvlogin
@rmtsrvname = N'TSU_Tmp',
@useself = N'TRUE',
@locallogin = NULL,
@rmtuser = N'Admin',
@rmtpassword = NULL
We both run the script, actually is a Stored Procedure, (see code below) on the same XP machine where SQL Server is running.
EXEC('INSERT INTO tblFcst
(StartBUCode, StartBUType, StartBUSeq, StartTrz, StartCty,
EndBUCode, EndBUType, EndBUSeq, EndTrz, EndCty,
FcstCreationPeriod, FcstValidForPeriod, Fcst, FcstExternalReference,
IsProcessed, IsSolved)
SELECT TSU.BUCodeSend, TSU.BUTypeSend, TSU.BuaNoSend, Null AS StartTrz, Null AS StartCty,
TSU.BUCodeRcv, TSU.BUTypeRcv, TSU.BuaNoRcv, Null AS EndTrz, Null AS EndCty,
TSU.[Current week], TSU.[Forecast for week], TSU.[Volume trp m3], TSU.[TSU_ID (Don''t touch me)],
0 AS IsProcessed, 0 AS IsSolved
FROM TSU_Tmp...tbl_TSU_trpm3 AS TSU;')
PS: it is run using an 'EXEC(String)' format as at compile time of Store Procedure the Linked Server is not existing and otherwise compile would fail.
We tried it with different files, in different locations. It always wors for me, never for him...
The files were not used by anyone else. The folder(s) where they were stored are open to "Everyone".
So I concluded it should be something linked to the User... :) But I really do not know what, as said apparently we have exactely the same setup in our Login profiles.
Any idea or suggestion is welcome.
Thanks
Luca

Hi Luca Lentati,
According to your description and T-SQL statement, we need to verify if the download and install the Microsoft.Jet.OleDB.4.0 as a provider.
If the 64bit SQL Server is running on the server, The error, the Microsoft.Jet.OleDB.4.0 is not support, I reommend you download and install the Microsoft.ACE.OLEDB.12.0 as a provider.
The error 7303 message indicates that the linked server does not have correct login mapping. You can execute the sp_helplinkedsrvlogin stored procedure to set the login information correctly. Also, verify that you have specified the correct parameters
for the linked server configuration.
In addition, if the issue still exists, I recommend you copy the access file to local Server, and create linked server between them , check if it can run well. If yes, it means that
the account which SQL server uses to run the service does not have read/write access to that file share.
There is an article about configuring a Linked Microsoft Access Server on SQL 2005 Server , you can review the following article.
http://www.aspfree.com/c/a/Microsoft-Access/Configuring-a-Linked-Microsoft-Access-Server-on-SQL-2005-Server/
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Running a SSIS package with SQL Job and Linked Server

I have a SSIS 2008 package. In one of the Script task I am calling a stored procedure which is using Openquery using linked server. I deployed this package with protection level as "EncryptWithPassword" and gave a password to the package.
Created a SQL job and edited its command line to include the password. If I login to SQL Server Mgmt Studio with Windows Authentication and run the job manually it runs fine. But when I schedule it then I get an error that "The Communication link to Linked
server failed".
Please help

Hi Vivek.B,
The issue should occur because the SQL Server Agent Service Account or SQL Agent Proxy account under which the job step runs doesn’t have sufficient permissions on the linked server.
If the job owner is the sysadmin fixed server role, the job can be run under the SQL Server Agent Service Account or a proxy account, then please make sure the SQL Agent Service Account or the proxy account has corresponding login on the linked server. If
the job owner is not a sysadmin fixed server role, the job must run under a proxy account. In this case, make sure the proxy account has a corresponding login on the linked server.
Reference:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/10/13/who-owns-my-job-and-who-runs-it.aspx
Regards,
Mike Yin
TechNet Community Support

Connect Non-SAP Oracle db (32bit) in sql 2005 (64 bit) using linked server

Hi,
I am connecting Oracle 10g database from SQL 2005 using linked server, in which i get the error
"Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "L2ORACLE".
OLE DB provider "MSDAORA" for linked server "L2ORACLE" returned message "Oracle client and networking components
were not found. " (Microsoft SQL Server, Error: 7303)
SAP Server with sql 2005 db is in 64 bit server / Windows 2003
Non-SAP Oracle 10g is in 32 bit windows 2003 server.
i have installed Oracle 64 bit client in the SAP Server and also copied the 64 bit version of dboraslib.dll to the DIR_LIBRARY path. I am able to view the oracle tables in the oracle client.
But, when i create the linked server, it gives the above error.
If i install 32 bit version of Oracle client in the SAP Server, i am able to create the linked server in the db level, but, it says "Work Process restarted, session terminated" message in the Z program in SAP.
The same works in the test environment where both are 32 bit servers. problem is when SAP server is in 64 bit and non sap is in 32 bit.
Please suggest.
Thanks and Regards,
Nagu

"Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "L2ORACLE".
OLE DB provider "MSDAORA" for linked server "L2ORACLE" returned message "Oracle client and networking components
were not found. " (Microsoft SQL Server, Error: 7303)
check the workprocess traces for errors (and/or SM21). It seems that the system is "not aware" that an Oracle client is installed.
64bit programs can´t load 32bit libraries/DLLs that´s why the workprocess dumps when you use the 32bit client.
Markus

Oracle InstantClient with Linked Server in Sql Server 2005

We are trying to connect ORACLE server from sql server 2005 using Linked Server Feature in SqlServer 2005
Generally Oracle Client software is needed for this activity in the sql server machine.
Can we use "Oracle InstantClient" instead of "Oracle Client Software" to connect ORACLE using Linked Servers ?
Please give us your views, any existing reports similar to this activity
Thanks & Regards,
Palani

Thanks for your reply
I agree that Oracle Client software is used to connect oracle from SQL SERVER 2005.
But my doubt is can we use Oracle InstantClient instead of Oracle Client software to connect oracle from SQL SERVER 2005
with respect to Oracle Instant Client - I would like to know the development steps (Not the installation steps of Oracle Instant Client in windows machine) to connect ORACLE server.
Thanks & Regards,
Palani

SQL linked server twice as slow in Windows 7 as XP

Similar Messages

Maybe you are looking for