Openquery SQL 2014

Is openquery still the way to query an Oracle linked server in SQL 2014? When researching how to setup an Oracle linked server I could have sworn I found an article saying openquery was deprecated, and instead we simple use "select * from linkedserver.owner.table".
But openquery is the only way I can get a query to work with my Oracle linked server in SQL 2014.
Thanks in advance.
André

... I found an article saying openquery was deprecated,
André, does the article did not refer to the SQL Native Client, whose last release was 2012?
According to the
What's New in SQL Server Native Client page,
"SQL Server 2014 installs SQL Server 2012 Native Client. There is no SQL Server 2014 Native Client"
and
"The OLE DB Provider in SQL Server Native Client was last updated in SQL Server 2012 Native Client. Developers who wish to use an OLE DB provider to connect to the latest version of
SQL Server must use the OLE DB provider that shipped in SQL Server 2012 Native Client".
In
OPENQUERY (2014): "This is subject to the capabilities of the
OLE DB provider".
José Diz Belo Horizonte, MG - Brasil
(Se encontrou a solução nesta resposta, ou se o conteúdo foi útil, lembre-se de marcá-la)

Similar Messages

SQL 2014 Exp Wont Install Win 8.1

Hello All,
Im really struggling to install SQL 2014 express on my windows 8.1 SL pc. x64
i installed SQL 2008 first but when i tried to install the studio management, it refused to work.
so i redownloaded the latest setups. ive tried both 32bit and 64bit
SQLEXPR_x86_ENU.exe 172mb
SQLManagementStudio_x86_ENU.exe 689mb
It just stays on the one screen after the landing page. ive left my pc for 6 to 8 hours...
ive tried this more than once... and no luck...
Note i have cleaned the registry and directorys each time.
Logs------------
http://1drv.ms/1pJFzTq
http://1drv.ms/1pJFAXC

I am little confused are you trying to install SQL server 2008 express or SQL server 2014 express.
You should first refer to
Hardware and Software requirements for installing SQL server 2014
You should also read Installing SQL server On windows 8
Finally when you are ready download
SQL server 2014 express
Edit: reg logs you posted it seems your machine where you are installing SQL server does not have internet connection. Internet connection is required for installation of SQL server 2014 express read Hardware and software requirements.
06) 2014-05-30 03:21:36 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: SQL Server Setup was not able to scan for product updates within 5 minutes. This can happen when there are Internet or network issues. ---> Microsoft.SqlServer.Configuration.SmartSetupExtension.MuSelectServerTimeoutException: SQL Server Setup was not able to scan for product updates within 5 minutes. This can happen when there are Internet or network issues.
Please revert if any Issue.
Hope this helps
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 Articles

(BUG??) Team Foundation Server 2013 Update 4 Support for SQL 2014

Scenario: On Windows 2012 R2 x64 I have installed SQL, Reporting Services & AS 2014 (applied all updates through Windows Update), SharePoint 2013 Foundation, and installed Team Foundation Server 2013 RTM (did not configure).
Before configuring TFS, I applied Update 4 to the server (not update 1,2 or 3 directly). When trying to configure I get the following error:
==========================
TF255146: Team Foundation Server requires SQL Server 2012 SP1 (11.00.3000) or greater. The SQL Server instance you supplied is version 12.0.2254.0.
TF400403: The Report Server instance specified is version 12.0.2254.0, the minimum supported version is 11.0.3000.
TF400070: A required version of a component is not installed on the application tier. You must exit the Team Foundation Administration Console and install a supported version of either SQL Server Analysis Services of the SQL Server Client Tools on the application
tier to ensure that the Analysis Services object model is present for warehouse processing.
====================================
My understanding is that as of Update 2 (or was it 3) that SQL 2014 was supported. However it appears if that particular update is not installed directly it bypasses the check. Can someone verify I am seeing the intended result or is this a bug?

Hi Jazzy,
Thanks for your post.
And thank you for sharing your experience here. It will be very beneficial for other community members having the similar questions.
All your participation and support are very important to build such harmonious/ pleasant / learning environment for MSDN community.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error in converting SQL 2014 Trial to Full version using VLKey

Hi,
I am currently trying to upgrade my SQL 2014 evaluation version to the full version.
I have purchased a Volume License for SQL Server 2014 Server/CAL and have extracted the product key from the ISO File.
I have verified this product key with the product activation department and it is confirmed that it is a valid product key "ProdKey3 SQL Svr Standard Edtn 2014 00204 PA/BP VL:GVLK Pre Pidded"
However, when i input the product key in to the server, it is showing me the error message:
The SQL product key is not valid, enter key from certificate of authenticity or SQL server packaging
Checked on the version of the evaluation and this is the edition - Microsoft SQL Server 2014.0120.2000.08
The site that I am activating the server on does not have any internet connection, does this affect the activation?
Would there be an alternate phone activation method for converting to Trial to Full?
Kindly Assist. Thank you.

Hi Julian,
Firstly, according to the error message, please ensure that your SQL Server installation file is not corrupt, and make sure you use corresponding license key matched the edition and version of SQL Server. For more details about the error, please review the
similar
thread.
Secondly, in addition to Ed’s post, you can also use the following command lines to upgrade SQL Server 2014 Trial to a full version.
Setup.exe /q /ACTION=editionupgrade /INSTANCENAME=<MSSQLSERVER or instancename> /PID=<PID key for new edition>" /IACCEPTSQLSERVERLICENSETERMS
Thirdly, for more detailed information regarding to the license issue, please call
1-800-426-9400,
Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the Guide to Worldwide Microsoft Licensing Sites to find contact information in your locations.
Thanks,
Lydia Zhang

SQL 2014 performance

We have a fresh install of SQL 2014 running on Windows 2012 R2 running in Production.
We tested this extensively first and most of our code ran as fast as SQL 2012 or slightly better.
Pure engine processes such as Backup jobs run about 30% faster.
However, now that we’re in Production for the first day we’re seeing some very sporadic performance.
For example, 90% of our jobs are running just fine. 10% of the jobs are running significantly longer.
Jobs that used to take 7-8 minutes are now running in 40 minutes plus.
Not only is this slowing down our server in general but it’s causing a lot of blocking issues.
We’re convinced this is a SQL 2014 issue and not hardware.
Using iometer we can tell that this server outperforms our old server.
SQL doesn’t always substantiate the numbers we’re seeing from iometer as far as performance compared to our old server.
We’re running on RTM, not Cumulative Update 1.
Our hardware is a beast of a server; DL580 G8, 384 GB ram, only 2 physical hard drives (running the OS/SQL) and the rest are Fusion iO cards.
We have 9 total Fusion cards for the database, log and tempdb.
Our old server is also a very robust server: DL380 G8, 384 GB ram, 48 physical drives and 2 Fusion iO cards for tempdb.
Has anyone else deployed SQL 2014? Has anyone else encountered these sporadic performance issues?
If so, did cumulative update 1 fix the issues?
Separate question: If I put my database in 2012 compatibility mode and do a backup, can SQL 2012 read the SQL 2014 backup?
Thanks in advance,
André
André

We applied CU2 last night. Things seem to be better this morning but we're still seeing some differences between SQL 2012. Here are 2 of the biggest issues we're seeing.
1 - views are slow. We have queries that use views that are taking forever. In some cases the view might be a simple "select 10 fields from table" type of views. If we change our query to use the base table instead of the view, the query
finishes very quickly. As an example, a query using the view takes 3 minutes. If we change the query to use the base table instead of the view it finishes in 5 seconds.
2 - inner joins are slow compared to "not exists" or "exists". Back when we migrated from SQL 2000 to 2008 we were told that joins were faster, so we migrated our code to use joins and our code flew. Now we're seeing performance issues on some,
but not all, queries that use joins.
3 - inner joins are not able to see the outside table. For example, this query worked just fine in SQL 2012, and it throws an error in 2014
select
top100
fromcustomers c(nolock)
inner
join(selectcorpnumber,fdate,code
fromdbo.FN_Customers_ParseCodes(c.rcode,c.corpnumber,c.fdate))r
onr.corpnumber=c.corpnumber
where
c.importtimestamp='2014-06-30
15:37:17.347'
and
c.customerid='123'
The error it throws is:
Msg 4104
,Level16,State1,Line
2
The multi
-part identifier "c.codes" could
notbe bound.
Msg 4104
,Level16,State1,Line
2
The multi
-part identifier "c.corpnumber" could
notbe bound.
Msg 4104
,Level16,State1,Line
2
The multi
-part identifier "c.fdate" could
notbe bound.
André

New table in msdb database of SQL 2014

Hi All, I've seen a table in MDSB database of SQL 2014 CTP version.
Table name is = smart_backup_files
Can any body explain the purpose of this table and where to use this one.
Asheesh pandey SQL server DBA

Smart Backup is a feature in SQL Server 2014 where in SQL Server can now manage your back up schedule using the new Managed Backup to Windows Azure feature. It determines backup frequency based on database usage patterns.
http://blogs.technet.com/b/dataplatforminsider/archive/2013/10/22/smart-secure-cost-effective-sql-server-back-up-to-windows-azure.aspx
smart-backup_files- This table is useful in monitoring the backup status of the managed backups\smart backups.
http://msdn.microsoft.com/en-us/library/dn449498(v=sql.120).aspx

Best practice configuration for SQL 2014 to achieve HA when hosted on Hyper-V 2012R2 cluster

Hi,
I've had a hunt around but so far I've not found a conclusive answer to my question. I am currently moving from a SQL 2008R2 (physical tin) failover cluster to a virtual environment build on Hyper-V 2012R2. I am building everything with SQL 2014
SP1.
I want to achieve the same level of high availability that I currently have and at the same time make sure that I can replicate (DR) data offsite (Azure) in the future. I have two options with SQL which are clustered instance (basically the same as
I have now) or AlwaysOn Availability Groups for database level HA.
I am unsure which is the best method to use when the SQL nodes are highly available guests on Hyper-V, trying to imagine how the guests will all move around in the case of a host server failure is a bit mind boggling to say the least.
I am leaning towards a instance failover but I would appreciate any input/advice etc.
Thanks
Rob

Hi Rob,
To start with I will not be installing SQL Server 2014 with SP1, as SP1 has bugs and Microsoft has disabled its download. See reference: http://www.eweek.com/database/microsoft-halts-sql-server-2014-sp1-downloads.html
With regards, I would go for AlwaysOn Availability Groups configuration, because it has several benefits:
You will get same amount of high availability you normally get with native cluster configuration, if you use AlwaysOn configuration. However, AlwaysOn configuration provides more granular high availability, and fail-over are invisible to the application,
if you using Availability Group listener to connect to server.
You can offload read-only workloads to secondary replica.
You can perform transaction log backups on secondary replica.
Reduce production downtime during patching or other planned work on the server.
So in short, you should use AlwaysOn configuration.
Regards,
Basit A. Farooq (MSC Computing, MCITP SQL Server 2005 & 2008, MCDBA SQL Server 2000)
http://basitaalishan.com
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Strange error in SQL 2014 - is it a bug?

Hi everybody,
I was writing a query to help in a recent thread and then got a very strange error:
declare @dt date = CURRENT_TIMESTAMP;
select convert(varchar(10), 103, @dt);
Run this code in SQL 2014 and see if it works for you or not. In BOL I didn't find anything indicating that CONVERT is not going to work with DATE type. Can you point me to BOL explaining the problem or confirm it's a bug?
UPDATE. Same error in SQL 2012. Does it mean I can not use CONVERT function with DATE type or some styles are not available? If yes, which codes I can use and which I can not?
UPDATE 2. I tried a few different styles and I got the same error message every time. That's new to me, looks like DATE type is not supported by CONVERT function at all?
For every expert, there is an equal and opposite expert. - Becker's Law
My blog
My TechNet articles

It should be declare @dt date = CURRENT_TIMESTAMP;
select convert(varchar(10), @dt,103);Correct me if I'm wrong.--Prashanth

Can't update SQL 2014 DB during web publish from Visual Studio 2013

According to Visual Studio 2013 I have "SQL Server Data Tool 12.0.40706.0" installed, which should allow me to update a SQL 2014 database but when I try to publish my web application I get the error: "Web deployment task failed. (Could not
generatedeployment script. Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database
platform service. Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider is not valid. You must make sure the service isloaded, or you must provide the full type name of a valid database platform
service. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXECUTING_METHOD.)" I can update the database fine if I go into the package managment console and run -UPDATE-DATABASE but I don't want to have to go into myweb.config, update it to point to the production
database, run the update command, and then change my web.config back everytime I try to update my database. What do I have to do to getthis working? I had no problems when I was on an Azure DB.

Actually problem seems to be related when web publish to remote server. I tried local web publish to sql2014 db and it works.
For remote server web publish works to sql 2012 express db but when try with sql 2014 express db on same server get bellow error.
Error message "The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider
is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service."
Any ideea what may be causing it? I have installed the sql server 2014 express with advanced services x86, exact same version as on my local machine, and also restarted server after install. Need install/configure anything else on server like SSDT 2014 to
make this work?
Cheers!

Finally! T-SQL Reference for SQL 2014 available for download!

With a mere delay of four month since the release, it is now possible to download the T-SQL Reference for SQL 2014 for your local copy of Books Online. Due to some reorganisations of the reference material on MSDN, the language reference was misisng from
the initial download.
To get the reference, you need to use Manage Help Settings, which you find the SQL 2014 program group. Select the option "Install content from online". Once all information has been loaded, scroll down to the SQL Server 2014 group and you will
SQL Server Language Reference with an Add option, which you should select.
Now, SQL 2014 uses Help Viewer 1.0, which is very poor, and versions 2.0 and 2.1 which ships with VS 2012/2013 is much more pleasant to use. Thanks to SQL Server MVP Simon Sabin, you can get the SQL 2014 into Help Viewer 2.x in this way. Go to
https://helpviewerredirector.codeplex.com/
save the file to a directory. Open a command prompt in that directory and run "HelpViewerRedirector download". Then in Help View, go to manage settings, and select install content from disk. Browse to the folder and select the files you want to see
in Help Viewer 2.1.
Erland Sommarskog, SQL Server MVP, [email protected]

To get the reference, you need to use Manage Help Settings, which you find the SQL 2014 program group. Select the option "Install content from online". Once all information has been loaded, scroll down to the SQL Server 2014 group and you will
SQL Server Language Reference with an Add option, which you should select.
If you need more detailed instructions on this part, see the comment from Microsoft added today (2014-08-01) to
http://connect.microsoft.com/SQLServer/feedback/details/859047/t-sql-reference-and-xquery-reference-missing-from-downloadable-version-of-bol-2014
Erland Sommarskog, SQL Server MVP, [email protected]

Issue while Upgrading to SQL 2014 from 2012. " The specified Edition upgrade is not supported."

Hello Team
I am seeing this issue while I am trying to do an in-place upgrade from SQL Server 2012 to SQL 2014. Both being Enterprise Editions I am still seeing the below error message in the Feature Upgrade checks.
" The specified Edition upgrade is not supported"
Please let me know if anyone else has faced this issue and any workarounds? I am not doing "Edition Upgrade", just wanted to upgrade same edition of 2012 to 2014.
SQL Server details that is being upgrade:
Microsoft SQL Server 2012 (SP1) - 11.0.3368.0 (X64)
May 22 2013 17:10:44
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
thanks

Hi Shanky_621
Thanks for the reply. Yes I was told that it is SQL 2014 Enterprise Edition. Is there a way to verify that? Also yes I did not select the free Evaluation or Express Editions.
Just run the setup you got for SQL server 2014 and you would reach to page where it would say enterprise or standard after that cancel the setup . Actually version number can be found from Mediainfo located in same folder where setup.exe is located but edition
cannot be found by that way.
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 Articles

New install of SQL 2014 Std MSDN. Get "The SQL Server product key is not valid. To proceed, re-enter the product key values from the Certificate of Authenticity (COA) or SQL Server packaging."

Trying to install a new version of SQL 2014 Std 64 or x86. Installing on Windows 8.1Pro 64bit machine.
I get:
"TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
The SQL Server product key is not valid. To proceed, re-enter the product key values from the Certificate of Authenticity (COA) or SQL Server packaging.
Error code 0x858C0017."
I looked at the summary log and that is the only error.
I made sure there were no other instances of SQL on this machine. Uninstalled all VS2013 and sql instances just in case. IF there is somewhere to check if a previous version or license is causing the issue, i would be glad to check.
Any help would be appreciated.

Hi,
Please read this thread with similar issue
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/bdd94577-515c-49fa-be44-008eacece057/installing-sql-server-2012-on-a-new-vm-error-code-0x858c0017?forum=sqlsetupandupgrade
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 Articles

Read Only SQL 2012 Replica DB on a SQL 2014 box

I have set up a data availability group between two SQl 2012 boxes on my windows cluster. they are failing over fine and synchronized as expected.
I want to add an additional read only replica on my SQL 2014 box which is also included in my windows cluster (so i can use this replica for reporting with 2014 In Memory features) the fail-over is still between the two 2012 boxes.
Problem is even tho i have set this replica to read only - yes, the database is always in - Synchronized / In recovery - so i can never connect to it.
Is this scenario possible?

Thanks David
Yes the whole point of this was to get access to real time data from within 2014, but the more i think about it the linked server still would not give me what i want as I belive the in memory is defined at table creation level.
With the tables being created in 2012 that would be a problem.
Thanks for the info mate.

SQL 2014 cluster installation on mounting point disks error: Updating permission setting for file

Dear all,
I am attempting to install SQL 2014 fail over cluster under a physical windows 2012 R2 server which have mounting point disks.
At the finish of setup I get the following error message.
Could you please help me on this?
Thanks
The following error has occurred:
Updating permission setting for file 'E:\Sysdata!System Volume Information\.....................................' failed. The file permission setting were supposed to be set to 'D:P(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;OICI;FA;;;CO)(A;OICI;FA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)'.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: go.microsoft.com/fwlink
I am using an administrator account which have all security rights (cheched on secpol.msc mmc) needed for installation.

Hi Marco_Ben_IT,
Do not install SQL Server to the root directory of a mount point, setup fails when the root of a mounted volume is chosen for the data file directory, we must always specify
a subdirectory for all files. This has to do with how permissions are granted. If you must put files in the root of the mount point you must manually manage the ACLs/permissions. We need to create a subfolder under the root of the mount point, and install
there.
More related information:
Using Mount Points with SQL Server
http://blogs.msdn.com/b/cindygross/archive/2011/07/05/using-mount-points-with-sql-server.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

SQL 2005 to SQL 2014

The following MSDN reference
http://msdn.microsoft.com/en-us/library/ms143393%28v=sql.120%29.aspx says
SQL Server 2014 supports upgrade from the following versions of SQL Server:
SQL Server 2008 SP3 or later
SQL Server 2008 R2 SP2 or later
SQL Server 2012 SP1 or later
However, in our testing, it is possible to upgrade from SQL 2005 SP4 to SQL 2014. There are no messages or detection errors when doing so. Will the final release of SQL 2014 support upgrading from SQL 2005 directly or will there be detection
added to the installation to prevent it?

Hello,
SQL Server 2005 won’t be supported as a valid upgrade path when SQL Server 2014 RTM is released as the article you posted states. The behavior you are seeing with the CTP version of SQL Server 2014 maybe is part due to some binaries of the SQL Server 2012
version still in use on the CTP version.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Openquery SQL 2014

Similar Messages

Maybe you are looking for