SQL 2012 64 Bit Linked Server to Excel 2013 64 Bit

What is the syntax for sp_AddLinkedServer to add an Excel 2013 64 bit Workbook as a Linked Server for 64 bit SQL Server 2012?

EXEC sp_addlinkedserver @server = N'ExcelDataSource',
@srvproduct=N'ExcelData', @provider=N'Microsoft.ACE.OLEDB.12.0',
@datasrc=N'C:\DataFolder\People.xlsx',
@provstr=N'EXCEL 12.0' ;
Refer http://technet.microsoft.com/en-us/library/ms190479.aspxAbout Provider download & Issues,http://social.msdn.microsoft.com/Forums/sqlserver/en-US/fbae9d36-e832-4706-a14e-629fc8d0c814/how-to-load-data-from-excel-2013?forum=sqlintegrationserviceshttp://social.msdn.microsoft.com/Forums/en-US/1d5c04c7-157f-4955-a14b-41d912d50a64/how-to-fix-error-the-microsoftaceoledb120-provider-is-not-registered-on-the-local-machine?forum=vstsdb
Regards, RSingh

Similar Messages

Lync 2013 and SQL 2012 on the same server

Hi,
I'm in the process of migrating Lync 2010 to Lync 2013. I have a clean install of Windows Server 2012 R2. Is it possible to install Lync 2013 and SQL 2012 on the same server or does it have to be on separate servers.
Thanks
P

Configure Separated SQL Server to use in an Enterprise deployment of Lync Server. Standard Edition servers use a collocated SQL Server Express version of SQL Server that is right sized for the workloads of a Standard Edition server.
Also you can refer below link
http://technet.microsoft.com/en-us/library/gg425848.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

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

Installing SQL 2012 BI on a server with Exchange 2010

I would like to create a new SBS-type network ... and I know that SBS2011 is dead, so I am looking at moving into the new Server 2012 world. I understand that Server 2012 Essentials has some really nice management and remote-access capabilities.
I definitely want to install Exchange 2010 on-premises and I know that it cannot be installed on Server 2012 Essentials, so I will have to deploy a second server running Server 2012 Standard. Not thrilled, but I can live with that (I miss SBS already).
I am also interested in installing SQL Server 2012 BI because I understand my POS (Point-Of-Sale) vendor should release a new SQL-based option in 2013 and I want to anticipate that and be ready.
I should have 15-17 users on this network without heavy use - mostly file + print sharing along with Exchange-based email. I do understand that Exchange takes up a lot of RAM, which is potentially a conflict with SQL Server, but I can put
8-12GB into each box. (Each box has two dual-core 2GHz AMD cpu's.)
So, my questions are:
Where should I best install SQL2012 BI?
Can Exchange 2010 and SQL 2012 BI live on the same box? If so, are there any tuning/install recommendations?
As you can see, I'm a newbie to the 2012 world and I appreciate any advice / pointers you can give.
Thanks!

Hello,
Please see the following article:
http://technet.microsoft.com/en-us/library/aa997379(v=EXCHG.80).aspx
“Running SQL Server on the same computer as a production Exchange mailbox server is not recommended. Both SQL Server and Exchange mailbox servers consume a large amount of memory and disk resources to operate optimally. Co-hosting SQL Server and Exchange Server
on the same computer in a production environment will likely lead to poor performance by one or both of the servers. Additionally, troubleshooting and securing such an installation is not well understood.”
“Move either Exchange Server or SQL Server off the computer. Completely removing one of these programs from the computer is recommended”
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Migrate Active Directory 2003 to 2012 R2 and Exchange Server 2007 to 2013.

My question is which one need to migration first. Active Directory 2003 to 2012 R2 and FFL & DFL or Exchange Server 2007 to 2013.
Md. Ramin Hossain

My question is which one need to migration first. Active Directory 2003 to 2012 R2 and FFL & DFL or Exchange Server 2007 to 2013.
Domain. For Exchange installation and upgrading to 2013, you need to make sure that your domain controllers can understand attributes of exchange 2013. Besides if you have DC/Exch on the same server which is 2003 is not supported. Because Windows Server
2003 is not supported.
Migrate your domain to at least 2008 R2 and then proceed with Exchange 2013.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

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]

SQL Server Memory Usage Peaks to 95% and its not releasing SQL 2012

We are currently running SQL 2012 64 bit, Lock Pages Enabled, 128 GB. We allocated Max Memory 112000, Min Memory to 0. We have a SQL Maintenace Job which backs up (Full Backup) of our server around 11PM at that time the SQL Server memory peaks to almost
96% even during full business hours we are constantly in the range of 56 to 60% but after 11PM within 10 minutes of the job it peaks to 95 or 96 Percentage and even after the job completes it's not releasing the memory back. I have to manually shut the sql
service and then restart at that time it comes back to normal.
Any suggestions/any help really appreciated.

Here are the details Memory is at 96% I still didn't restart...Please any help appreciated...The memory detals is for 24 hours I restarted the service around 11AM before I posted my previous message..
Memory Used by SqLServer: 119329
Locked Pages Used SQLServer : 105969
Total VAS in MB : 8388607
Process Physical Memory Low : 0
Process Virtual Memory Low : 0
Max Memory set to :112000
Out of 128 Memory Last 24 hours the memory usage in %
Percent Memory Used - Total Memory is 128.0 GB
Last 24 Hours
DATE / TIME
Memory Used
19-Dec-14
11:46 PM
96.24659602
20-Dec-14
12:46 AM
96.24578349
20-Dec-14
1:46 AM
96.25146739
20-Dec-14
2:46 AM
96.24345652
20-Dec-14
3:46 AM
96.27311834
20-Dec-14
4:46 AM
96.28947067
20-Dec-14
5:46 AM
96.18931325
20-Dec-14
6:46 AM
96.09323502
20-Dec-14
7:46 AM
96.07915497
20-Dec-14
8:46 AM
96.07906977
20-Dec-14
9:46 AM
96.0784111
20-Dec-14
10:46 AM
96.07415009
20-Dec-14
11:46 AM
26.03422141
20-Dec-14
12:46 PM
33.57474359
20-Dec-14
1:46 PM
39.466561
20-Dec-14
2:46 PM
41.85940742
20-Dec-14
3:46 PM
43.89071274
20-Dec-14
4:46 PM
45.80877368
20-Dec-14
5:46 PM
46.49493281
20-Dec-14
6:46 PM
46.68486468
20-Dec-14
7:46 PM
46.69701958
20-Dec-14
8:46 PM
46.69994736
20-Dec-14
9:46 PM
57.5012455
20-Dec-14
10:46 PM
96.25695419
I verified its a sqL job and still my memory is 95%
It peaeked at 10:46PM and here are the details of the SQL job which started at 10:30
Progress: 2014-12-20 22:30:04.39
Source: Check Database Integrity Task Executing query "USE [DATASTORE] ".: 50% complete End Progress Progress: 2014-12-20 22:43:06.10
Source: Check Database Integrity Task Executing query "DBCC CHECKDB(N'DATASTORE') WITH NO_INFOMSGS ".: 100% complete End Progress
Progress: 2014-12-20 22:43:06.11 Source: Check Database Integrity Task Executing query "USE [ETL_Proc] ".: 50% complete
End Progress Progress: 2014-12-20 22:46:52.56 Source: Check Database Integrity Task Executing query "DBCC CHECKDB(N'ETL_Proc')
WITH NO_INFOMSGS ".: 100% complete End Progress Progress: 2014-12-20 22:46:52.64 Source: Back Up Database Task
Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 20% complete End Progress
Progress: 2014-12-20 22:46:52.64 Source: Back Up Database Task Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".
: 40% complete End Progress Progress: 2014-12-20 22:46:52.64
Source: Back Up Database Task Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 60% complete
End Progress Progress: 2014-12-20 22:46:52.64 Source: Back Up Database Task
Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 80% complete End Progress
Progress: 2014-12-20 22:46:52.64 Source: Back Up Database Task
Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 100% complete End Progress
Progress: 2014-12-20 22:46:55.63 Source: Back Up Database Task
Executing query "BACKUP DATABASE [ReportServer] TO DISK = N'P:\SQL...".: 100% complete
End Progress Progress: 2014-12-20 22:46:56.55 Source: Back Up Database Task
Executing query "BACKUP DATABASE [ReportServerTempDB] TO DISK = N'...".: 100% complete End Progress Progress: 2014-12-20 22:46:57.35
Source: Back Up Database Task Executing query "BACKUP DATABASE [dbamaint] TO DISK = N'P:\SQL_Bac...".: 100% complete End Progress
Progress: 2014-12-20 22:51:13.08 Source: Back Up Database Task
Executing query "BACKUP DATABASE [DATASTORE] TO DISK = N'P:\SQL_Ba...".: 100% complete End Progress
Progress: 2014-12-20 22:51:52.72 Source: Back Up Database Task
Executing query "BACKUP DATABASE [ETL_Proc] TO DISK = N'P:\SQL_Bac...".: 100% complete End Progress Progress: 2014-12-20 22:51:54.87
Source: Rebuild Index Task Executing query "USE [ReportServer] ".: 0% complete End Progress Progress:
2014-12-20 22:51:54.88 Source: Rebuild Index Task Executing query "ALT... The package executed successf... The step succeeded.

Linked Server to MS Access mdb file and exclusivity??

I've got an SQL database running on SQL Server 2008. From this server, I have a linked server to an Access database (access 2003).
In my database I have a stored procedure that I want to query the access database (linked server) and insert / update some rows in one of my SQL tables.
The linked server is setup without an ODBC DSN (though, I have tried it with one and still get the same results).
When I run the stored procedure RDP'd onto the sql server, it runs without issue. When I run the stored procedure from management studio from my machine, I get "It is already opened exclusively by another user, or you need permission to view its
data"
Unfortunately, this access mdb file is pulled from all over our organizatoin - a sin from a long time ago - but I do know that in both instances, the file is still in use by others.
My SQL Server and file server where the MDB file exists are both a member of the same domain. Also, the account the SQL Service runs under is a domain account as well.
Does this make any sense?
Thanks
sb

Hi kumar,
According to your description, when you create an linked server in SQL Server 64 bit to connect to the Access database 32bit , usually, the error 7399 and 7350 will occur. As other post, you need to install SQL Server 32bit. Or you can uninstall 32bit office
products and install 64bit Microsoft Access Database Engine. For creating Linked Server, if you run on a 64bit environment we need to download
Microsoft Access Database Engine 2010 Redistributable from Microsoft and install suitable version of software on the machine.
For more information, see:
http://calyansql.blogspot.jp/2013/02/fix-cannot-initialize-data-source.html
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL 2012 Management Studio Remote Servers Service Status Slow/Stops Working

This is a huge annoyance. I manage about 50 SQL instances of SQL Server versions 2005-2012 and I noticed that it takes 1-2 seconds to load the service status (green arrow) on each individual server. If you then connect to a server, you have to
wait for all the statuses to be loaded first in the Registered Servers list before it loads the statuses for servers in the Object Explorer. This happens whether the servers are registered in Local Server Groups or Central Management Servers, and whether
I have access to all servers (as windows local administrator and sa), or not. It also happens regardless of whether I run as Administrator or normally on my instance of SSMS (which is SQL 2012 Development on Windows Server 2008 R2).
These servers are also registered in alphabetical order by group and server name, which means that if I have "DEV" groups, they will be registered before "PROD", unless I rename accordingly. It sometimes takes a few minutes, if
I'm lucky, to get a server I connect to to load, which means I can't use SSMS to really manage any remote servers and start/stop/pause/resume/restart services.
Worse, sometimes due to a server becoming unavailable (due to updates/patches/failovers), SSMS is unable to load the service statuses anymore for any new server connections made to object explorer, resulting in the loss of ability to view/change service statuses.
In this case, there is no way to recover (Refresh of Central Management Servers does nothing), except to close SSMS and open it again, and then wait again for all the statuses to load.
I have lived with this since first installing SQL, and regardless of the Windows Updates and SQL patches applied, the problem has never gone away. This also happens if I load SSMS in Windows Server 2012. Its starting to become a huge issue now
that I have to patch several servers each month.
I have already checked WMI permissions, GPO, firewall, etc. as per all the suggestion on the internet, including this post
http://www.sqlservercentral.com/Forums/Topic825246-146-1.aspx. None of these suggestions have made a difference, as my real problem is one of connectivity and performance, and
not security, which most of these suggestions apply to. Of note, all servers are in the same domain, firewall is disabled across the board, correct permissions for local administrators exist for remote registry settings, WMI, GPO, etc, and all service
accounts and windows accounts that are used are local admins and sysadmins.
My work-around has been to delete the Central Management Server and any local server group registered servers, close and re-launch SSMS, and then connect to a server I'm interested in via Object Explorer. Otherwise, close and re-launch will take forever.
My other alternative is to RDP into the remote server and manage services via SQL Configuration Manager locally.
If anyone has any ideas on how to fix this, or make it go faster, I'd really appreciate it.
Diane

Hi Satish,
Thanks for taking the time to reply. Yes, I actually am already using work-arounds (i.e. methods other than SSMS) to accomplish my tasks. My issue is that this is supposed to be working and provide a nice GUI so that you can easily visualize
any issues, and address them directly, without having to hodge-podge access via scripts or 3rd-Party tools.
Since no one else has any comments, I guess there are no plans to make remote server administration work with SSMS properly then, and that kludge methods are the only ones being advocated.
Diane

Installing SQL 2008 / SQL 2012 in a DMZ covered by RODCs

Hello guys,
I'm trying to install SQL 2008 (tried also SQL 2012) in a W2008R2 server that lives in a DMZ site covered by a couple of RODCs.
The RODCs have full access to the RWDCs, but the traffic is blocked from the rest of computers in the DMZ to the RWDCs.
Every time I run the wizard to install SQL server, it fails when trying to setup a domain user to run SQL services
(“Server configuration >> Service Account” step). When I temporary allow the communication from that SQL Server to one of the RWDCs, it works.
I have obviously cached and prepopulated passwords in the RODCs and I am using Domain Admins and non-domain admins accounts.
We have more than 30 windows member servers authenticating against those RODCs in the DMZ and everything works fine.
Any ideas why the SQL installation wizard cannot authenticate against a RODC? I have been googling and I didn’t find anything!
Btw, I have already posted a similar thread in the SQL forum. They suggested to "install SQL Server with a local Windows
account and then change the SQL Server service account with to the Domain account". That actually works, but I'd like to find out what is wrong my RO AD setup or this is a just an expected
behavior in SQL installations covered by RODCs.
Thanks.

Any update about the issue?
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

Linked Server error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON' between sql server 2005 32 bit and sql server 2012 64 bit

Hi All,
Here the linked server is created between sql server 2012 64 bit and sql server 2005 32 bit. I am getting the below error when i try to access linked server from third server. I have created linked from Instance 1 to Instance 2. When i access it from
instance 3 i am getting the below error. SPN setting has been done between these 2 servers. Also the option 'Trust the delegate' is enabled for the both the service account.
'Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Appreciate your quick response.
Vikas.M.S

Hello,
Please read the following resources:
http://www.databasejournal.com/features/mssql/article.php/3696506/Setting-Up-Delegation-for-Linked-Servers.htm
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea26de43-4c6b-4991-86d7-e1578f107c92/linked-server-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldataaccess
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

How to create a Linked Server from SQL Server 2012 to Postgresql

Hi, I am working on a third party application which is using Postgresql version 9 database and I am trying create a linked server in SQL Server 2012 using the below stored procedure.
EXEC master.dbo.sp_addlinkedserver @server = N'LINKEDSERVERPOSTGRES', @srvproduct=N'PostgreSQL',
@provider=N'MSDASQL', @provstr=N'Driver=PostgreSQL;uid=pguser;Server=pghost;database=pgdatabase;pwd=somepassword'
Error: Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server.
I have no clue if a jdbc provider exists in SQL Server to connect to Postgresql or what the right provider is? Could you please let me know if there's a workaround to achieve this.
Thanks in advance............
Ione

See if this helps
http://www.postgresonline.com/journal/archives/46-Setting-up-PostgreSQL-as-a-Linked-Server-in-Microsoft-SQL-Server-64-bit.html
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Which version of sql server 2012 or 2014 is best for sharepoint 2013.. Any excellent comparision available please let me know..

Which version of sql server 2012 or 2014 is best for sharepoint 2013.. Any excellent comparision available please let me know..i mean enterprise version BI version or standard version.. i just need a detailed comparison if available please thank you

As of right this very second, SQL Server 2014 is not supported. SharePoint 2013 supports:
One of the following:
The 64-bit edition of Microsoft SQL Server 2012.
The 64-bit edition of SQL Server 2008 R2 Service Pack 1
Hardware and software requirements for SharePoint 2013
Edit: I may be mistaken. It looks like the April 2014 CU adds support for SQL Server 2014. If this is the case generally going with the latest SQL Edition provides you with the latest SQL functionality. I'm not aware of any SharePoint features that would
make use of functionality that is new to SQL Server 2014 but this could change with a future service pack.
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Error installing SQL Compact 3.5 sp2 on 2012 64-bit server.

Sql Compact 3.5 sp2 will not install on 2012 64-bit server. I'm getting an error that the replication components need to be installed for Sql 2008. My Sql Server is at sp1 (11.0.3393) and is replicating currently to another Sql Server.
Both 64 and 32 bit installs gives me this error.

First, you need the latest tools, build 8089, download links here:
http://erikej.blogspot.dk/2010/08/sql-server-compact-35-sp2-downloadable.html
And secondly (I assume this is a 2 server configration, with separate IIS and SQL Server?) - you need to install the 2012 database engine as well, to get the replicaation components installed (just stop and disable the SQL Server service after install, so
it does not consume any unneccesary resources)
And thirdly, SQL 2012 SP1 is not enough, you must install the latest CU, both on the IIS server and on the database server.
Let me know if that was unclear.
Please mark as answer, if this was it. Visit my SQL Server Compact blog http://erikej.blogspot.com

Memory leak issue with link server between SQL Server 2012 and Oracle

Hi,
We are trying to use the linked server feature with SQL Server 2012 to connect SQL server and Oracle database. We are concerned about the existing memory leak issue. For more context please refer to the link.
http://blogs.msdn.com/b/psssql/archive/2009/09/22/if-you-use-linked-server-queries-you-need-to-read-this.aspx
The above link talks about the issues with SQL Server versions 2005 and 2008, not sure if this is still the case in 2012. I could not find any article that talks about if this issue was fixed by Microsoft in later version.
We know that SQL Server process crashes because of the third-party linked server provider which is loaded inside SQL Server process. If the third-party linked server provider is enabled together with the
Allow inprocess option, the SQL Server process crashes when this third-party linked server experiences internal problems.
We wanted to know if this fixed in SQL Server 2012 ?

So your question is more of a information type or are you really facing OOM issue.
There can be two things for OOM
1. There is bug in SQL Server which is causing the issue which might be fixed in 2012
2. The Linked server provider used to connect to Oracle is not upto date and some patch is missing or more recent version is to be used. Did you made sure that you are using latest version.
What is Oracle version you are trying to connect(9i,10g, R2...)
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

SQL 2012 64 Bit Linked Server to Excel 2013 64 Bit

Similar Messages

Maybe you are looking for