SQL 2014 Issues

I have setup SQL 2014 for my DB server, however the pre-requisite check is failing. When I checked the compatibility on TECHNET, 2014 is listed as supported for SCCM 2012 R2. Can someone let me know if there is a patch that's needed.
Thanks in advance

ConfigMgr 2012 R2 are supported with SQL 2014.
Just use the 3020755 hotfix.
More info:
https://stevethompsonmvp.wordpress.com/2015/02/11/configmgr-2012-r2-support-for-sql-server-2014/
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

Similar Messages

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é

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

SQL 2014 Azure Managed Backup Issues

Hi all,
We recently enabled Azure Managed Backup on one of our DEV boxes running on SQL 2014. After turning on extended mail notifications, we have begun seeing several errors getting logged. Some of them are as follows:
[SSMBackup2WAAdminXevent] Database Name = WS_AppOneInterface, Database ID = 13, Stage = VerifyJobOutcome, Error Code = 3271, Error Message = Processed 7581 pages for database 'WS_AppOneInterface', file 'WS_AppOneInterface_log' on file 1. [SQLSTATE 01000]A
nonrecoverable I/O error occurred on file "https://******.blob.core.windows.net/********-mssqlserver/WS_AppOneInterface_452a51d376e54b92a284132f52ead429_20140831221756-05.log:"
Backup to URL received an exception from the remote endpoint. Exception M
[FileRetentionAdminXevent] Type = SqlError, Code = 3292, Stage = Undefined, Message = A failure occurred while attempting to execute Backup or Restore with a URL device specified. Consult the Windows Event Log for details.
RESTORE HEADERONLY is terminating abnormally., Additional Info = N/A.
When I look at the folder in Azure storage, I see a ton of log & bak files. So are the backups working or not working? How can I tell? If SQL encounters an error, does it retry? How often? How can I check the backup status of each database on the server?
Thanks,
Param
Param R

Hello,
The following article explains about a similar error and it mentions the cause of the error could be a proxy configuration:
http://msdn.microsoft.com/en-us/library/jj919149.aspx
The following article may help you troubleshoot this error too:
http://msdn.microsoft.com/en-us/library/dn449495.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Workflow Manager Configuration Issue Windows Server 2012 R2 / SQL 2014

Hello All,
Environment: SharePoint 2013 Enterprise with SP1
Farm consists of
2 App Server, 2 Web Server and 2 SQL Servers all the server have Windows 2012 R2
OS . The SQL backend is SQL Server 2014
Installed Workflow manager on the Web server, the configuration ran fine without any errors. Trying to browse the workflow management site via IIS Manager encountered Certificate Error clicked Continue to this website which gives a HTTP 403 Forbidden and
following detail message
This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.
Checked the web site Workflow Management Site in the IIS manager which has only one folder bin . I was not able to submit the Screenshot
I have installed the latest patch for the Workflow manager and the Service Bus
Question I have
Should there be more folder under the Workflow Management Site.
Why is the Web site not showing the web page
Is workflow manager supported for Windows Server 2012 R2 and SQL 2014
Thanks
Dhanraj

Hi Dhanraj,
I captured the screenshot from my IIS Manager on workflow server. There is only bin folder under Workflow Management site
If I browser workflow host uri from IIS Manager
https://localhost:12290, I received certification error, and I chose the continue to this website, it returned me as follow:
From the link: http://support.microsoft.com/kb/2902007/en-us It is supported on Windows Server 2012 r2 if you have install latest update.
Here is an article which talks about error:
http://www.sp2013blog.com/Lists/Posts/Post.aspx?ID=36
In addition, here is the reference for troubleshooting workflow manager 1.0 management:
http://msdn.microsoft.com/en-us/library/jj193529(v=azure.10).aspx#AnalyzingWorkflowManagementLogs
You could also open SharePoint Designer 2013 and see if you could create a workflow on platform 2013.
Regards,
Rebecca Tu
TechNet Community Support

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

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

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

SQL 2014 - Group Membership for sysadmin permissions not working

I am using SQL 2014 on Windows Server 2012 R2 and am running into a permission issue. During the install I specified the local server's Administrators group as well as my specific domain account to have sysadmin privileges.
The issue is that accounts that are a member of the local server's administrators group can't even login to SQL Server Management Studio unless they are specifically granted permissions for their account (my domain account works fine as it has a specific
credential in SQL).
The log just gives the following error:
Login failed for user 'domainname\username'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
Error: 18456, Severity: 14, State: 11.
I haven't had this issue in previous versions. Is there something that must be done differently in 2014 to grant permissions to groups?

Hi, something like
this?
Bye
Questo post è fornito "così com'è". Non conferisce garanzie o diritti di alcun tipo. Ricorda di usare la funzione "segna come risposta" per i post che ti hanno aiutato a risolvere il problema e "deseleziona come risposta"
quando le risposte segnate non sono effettivamente utili. Questo è particolarmente utile per altri utenti che leggono il thread, alla ricerca di soluzioni a problemi similari. ENG: This posting is provided "AS IS" with no warranties, and confers
no rights. 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.

Backup Sharepoint 2013 SP1 Farm with SQL 2014 RTM "Always On" using System Center 2012 R2 Data Protection Manager

Is backing up and Restoring SharePoint 2013 SP1 Farm with SQL 2014 RTM "Always On" High Availability now supported using "System Center 2012 R2 Data Protection Manager"?
I cannot find information anywhere.
Regards,
Igor

This is a DPM supportability issue, I believe. Last I heard, no it was not supported. SharePoint 2013 does not support SQL 2014 until the April 2014 CU. The CU should be out soon, although it appears to have been delayed (usually comes out on Patch Tuesday,
which was this past Tuesday).
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

DPM 2012 R2 CU4 protecting SQL 2014 AlwaysOn AG with Failover Cluster vs. DR location

Hello!
We have a problem protecting any Database of SQL 2014 AlwaysOn Availability Group with SQL Failover Cluster Instance when moved to DR location. Everything is protected using DPM 2012 R2 CU4 from Primary location.
FACTS
- all servers are Windows Server 2012 R2
- all servers are Virtual (except Hyper-V hosts obviously:)
- that means virtualization is based on Windows Server 2012 R2 Hyper-V
- all clusters (SQL, Exchange,...) are Guest Clusters on Hyper-V
- SQL 2014
- DPM 2012 R2 CU4
- Primary and DR location
SETUP
SQL
- Primary location: SQL 2014 Guest Cluster with SQL Failover Cluster Instance using Shared VHDX disks
- DR location: SQL 2014 Standalone using VHDX disks
- AlwaysOn Availability Group expands between the primary and DR location.
DPM
- Primary location: DPM 2012 R2 CU4
- DPM 2012 R2 CU4 Agents installed on every possible SQL 2014 Server.
SCENARIO
- DPM is backing up all the SQL Databases normally as long as they exist on any SQL Cluster Node on Primary location.
- As soon as any Database is moved to DR location, that Database is not backed up anymore with the following error.
DPM ERROR
Starting synchronization on SqlServerName\DatabaseName failed:
Error 104: An unexpected error occurred while the job was running.
Error details: The system cannot find the path specified (0x80070003)
Recommended action: Retry the operation.
TROUBLESHOOTING
- Tried to modify SQL Protection Group in DPM Server while Database was active on DR location
> error enumerating volumes or drives D:\, E:\, F:\ (I don't have exact error atm)
> this looks like DPM is not aware that DPM is active on DR location to me
- Checked Technet, blogs and forums; no useful information
QUESTION
Is this expected or by-design behavior? Is this a bug? I am aware there were quite some issues backing up AG's from DPM 2012 SP1 ans SQL 2012 on.
Does anybody have a lab of that kind to try it out?
Thank you!
Best Regards,
Damjan Grimšič
Lpd

OK. The issue has been resolved. Issue was related to possible Disks Owners in Failover Cluster Manager Console for SQL Cluster.
In Primary's site SQL Cluster Failover Manager Console / Storage / Disks.
SQL Server(s) from Secondary location need(s) to be unchecked as Possible owner(s) in Advanced Policies for all relevant Volumes.
Lpd

Gathering physical memory for SQL 2005..SQL 2014

Hi All,
I'm trying to write a query to gather physical memory across my SQL servers (from SQL 2005 to SQL 2012).
However, the sys.dm_os_sys_info DMV (the column for physical memory) is not the same after the switch to SQL 2012+.
Here is the original query:
SELECT
@@SERVERNAME AS ServerName,
CASE WHEN LEFT(CAST(serverproperty('productversion') as char), 1) = 9 THEN '2005'
WHEN LEFT(CAST(serverproperty('productversion') as char), 4) = 10.0 THEN '2008'
WHEN LEFT(CAST(serverproperty('productversion') as char), 4) = 10.5 THEN '2008R2'
WHEN LEFT(CAST(serverproperty('productversion') as char), 2) = 11 THEN '2012'
END AS MajorVersion,
SERVERPROPERTY ('productlevel') AS MinorVersion,
SERVERPROPERTY('productversion') AS FullVersion,
SERVERPROPERTY ('edition') AS Edition,
SERVERPROPERTY('collation') as Collation,
cpu_count as CpuCount,
physical_memory_in_bytes/1024/1024 as PhysMemMB
FROM [sys].[dm_os_sys_info]
If I run that on SQL 2014, it fails because 'physical_memory_in_bytes' is now called 'physical_memory_kb'
I tried to do an IF..THEN..ELSE:
IF (cast(serverproperty('productversion') as char) like '11.%')
Then change the query accordingly but it would fail because i guess when it tried to parse the whole code, one of the T-SQL variations would have a column that did not exist in that particular version of SQL Server.
Is there a way I can get physical memory across SQL 2005..SQL 2012 or rewrite the T-SQL above to be able to run on both?
Thanks in advance

Oh it seemed like you are asking SQL Server memory. the name for physical memory column ha changed only in SQL Server 2012. I wrote below script just first run select SERVERPROPERTY('ResourceVersion') to get exact resource database version of
SQL Server 2012 and then replace it in below script
IF cast ( SERVERPROPERTY('ResourceVersion') as char (10) )= '11.00.2000'--2012 resource database version
select (physical_memory_kb/1024)as Physical_mem_MB from sys.dm_os_sys_info
else
select (physical_memory_in_bytes/1024/1024) as physical_mem_MB from sys.dm_os_sys_info
Edit: A more optimized query
If cast (LEFT( CAST(SERVERPROPERTY('ResourceVersion') AS VARCHAR(20)),2) as INT) in ('11','12')
select (physical_memory_KB/1024) as Physical_Mem_MB from sys.dm_os_sys_info
--else it uses for 2005-08R2
else select (physical_memory_in_bytes/1024/1024) as Physical_Mem_MB from sys.dm_os_sys_info
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
Hi Shanky,
Doesn't work and that's what I meant in my initial post..when I run that code against a SQL 2012 instance, it parses fine but when I execute it I get:
Msg 207, Level 16, State 1, Line 6
Invalid column name 'physical_memory_in_bytes'.

Migration of the database from Microsoft SQL 2014 Express to Microsoft SQL 2012 Server

I posted a similar thread yesterday, and I realized that there was a serious typo.
Link: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b3e201ea-6c7c-43a4-8908-842b714ea451/migration-of-the-database-from-microsoft-sql-2014-express-to-microsoft-sql-2012-server?forum=sqlservermigration
Therefore, I made a decision to post another thread right now.
I am
writing to ask if there are any known issues when migration from MS SQL 2014 Express to MS SQL 2012 Server version. Are there any step-by-step instruction on how I can go about doing this?
Looking forward to your response. Thank you for your time.
Regards,
Jeff Yoo

Hello,
SQL Server 2012 setup program won’t allow you to perform a downgrade from SQL Server 2014 Express Edition. Backup/Restore
and Detach/Attach won’t help you either.
One option you have left is using SQL Server Import/Export Wizard as explained on the following article.
http://www.mytechmantra.com/LearnSQLServer/Downgrade_SQL_Server_Database_P1.html
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL 2014 RTM and Sql 2008r2 standard side by side installation ..

We are planning on reconfiguring our database server and then installing SQL 2008 R2 Standard edition in a side by side installation with SQL 2014 RTM. I have researched a little, and have not seen any major issues when planning this type of configuration.
Are there any issues that may occur with this?
2008 R2 will be in the default instance, and 2014 will be using a named instance. We do foresee uninstalling 2008 R2 after a period of time, and moving all of our databases to 2014 after testing has been performed. Once we uninstall 2008 R2, will we be able
to install a default instance of 2014? Are there any special steps that need to be taken to do that?

Hello,
If possible install the SQL Server 2008 R2 instance first, then install SQL Server 2014. Through the years, the formula
of installing the older versions of SQL Server first has proved to be a winner for me.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SSIS Development SQL 2014

I've searched and read that SQL Data Tools is gone in SQL 2014. It seems as though it's been replaced, and is currently pulled, by a plugin for VS2013.
My question is this; is SQL Server 2014 not a complete product any longer? I don't have VS 2013, so what am I supposed to do? I need to develop/modify my SSIS packages and we're about to migrate to SQL 2014. I can't believe all the tools
I need no longer come with the install of SQL 2014 - this is extremely disappointing.
Thanks in advance
André

Hi Andremg,
To do SQL Server Business Intelligence development, you don’t need to install Visual Studio. The specif version of BIDS/SSDT just uses specific Visual Studio shell, and can be integrated into the corresponding Visual Studio. The BIDS/SSDT is a different
product and works independent of Visual Studio.
Since the relase of SQL Server 2014, the SQL Server Data Tools used for Business Intelligence development is not shipped with SQL Server installation. To get the SSDT-BI Tools, we need to download it from the Micrsoft Download Center manually.
Currently, there are two versions of SSDT-BI Tools avaiable for SQL Server 2014 BI development:
Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013
Microsoft SQL Server 2014 CTP2 Data Tools - Business Intelligence for Microsoft Visual Studio 2012
Actually, the SQL Server Data Tools - Business Intelligence (SSDT-BI) for Visual Studio 2013 is the native SSDT for SQL Server 2014 RTM. However, it is not available in the Download Center due to some compatiblity issues currently. So, we can temporarily
use the SQL Server 2014 CTP2 Data Tools - Business Intelligence for Microsoft Visual Studio 2012 for SQL Server 2014 BI development. Once the SSDT-BI for Visual Studio 2013 is back, we can install it and use it instead.
Besides, please understand that BI projects created in SQL Server 2014 CTP2 SSDT-BI for Visual Studio 2012 can be opened and eidted in SSDT-BI for Visual Studio 2013 without any problems. So, we don't need to worry about the continuity of the BI development.
In addition, as Kieran said, SSDT-BI Tools is a client tool and seldom installed on a production server.
Regards,
Mike Yin
TechNet Community Support

SQL 2014 Issues

Similar Messages

Maybe you are looking for