SQL 2014 license for SQL 2008

Hi,
I'm purchasing SQL 2014 license.
Can I use the SQL 2014 license for SQL 2008 or 2012.
Thanks,
Sathish
Sathish

Hi Sathish,
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.
Regards,
Elvis Long
TechNet Community Support

Similar Messages

Do we need to pay anything extra for IIS when i have already bought a license for windows 2008 R2 Stanard server license

Hi,
I want to understand the licensing structure of Microsoft windows 2008 server standard edition.
If i buy a Microsoft windows 2008 server standard edition license ,can i activate the IIS in that without any extra cost involved ?
Can i use this license on commercial purpose for my website deployment ?
How much it will cost for me ?
Regards,
Deepak

Hello,
if you want using the IIS role on the Windows Server for your Website you Need only the Server License without to purchase the CALs or External Connector.
thanks
diramoh

Extend license for evaluation versions of server 2008 rs and sql 2008 rs

We had to stop our testing because of seasonal business requirements and now have only 11 days before the expiration of our trial versions of SQL Server 2008 R2 and Windows Server 2008 R2. How do we extend the license for 60 days to complete our testing
and start the move to a new production system?

Hi,
Please refer to following article and check if can help you.
Extending
Your Activation Grace Period on Windows Server 2008 and 2008 R2
However, as GreenlightTech suggested, purchasing licenses and activating will be a better option before activation
Grace Period
expired.
If anything I misunderstand or any update, please feel free to let us know.
Hope this helps.
Best regards,
Justin Gu

SQL Server 2014 License compatibility

I have SQL Server 2014 core base Licenses. Can I use these licenses for SQL Server 2005 and SQL Server 2008 and 2008R2 as well?

Try the below:
Microsoft India Contact Details:-
Toll Free Number:- 1800-11-1100
Toll Free Number:- 1800-102-1100
Toll Phone Number:- +91-80-40103000
http://www.microsoft.com/en-in/licensing/how-to-buy/how-to-buy.aspx

Issue With Report Builder After Installing SP3 for SQL 2008 R2

Hello. We are experiencing an issue with Report Builder 3.0 since installing SP3 for SQL 2008 R2 over the weekend. You can no longer launch Report Builder from the Reporting Services URL (http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application
      Server  : Microsoft-HTTPAPI/2.0
      X-AspNet-Version: 2.0.50727
Application url   :
http://dicomweb/ReportServer/ReportBuilder/RptBuilder_3/MSReportBuilder.exe.manifest
      Server  : Microsoft-HTTPAPI/2.0
      X-AspNet-Version: 2.0.50727
IDENTITIES
Deployment Identity  : ReportBuilder_3_0_0_0.application, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86
Application Identity  : MSReportBuilder.exe, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86, type=win32
APPLICATION SUMMARY
* Online only application.
* Trust url parameter is set.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of
http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application resulted in exception. Following failure messages were detected:
  + File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [10/15/2014 9:35:56 AM] : Activation of
http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application has started.
* [10/15/2014 9:36:29 AM] : Processing of deployment manifest has successfully completed.
* [10/15/2014 9:36:29 AM] : Installation of the application has started.
* [10/15/2014 9:36:31 AM] : Processing of application manifest has successfully completed.
* [10/15/2014 9:36:35 AM] : Found compatible runtime version 2.0.50727.
* [10/15/2014 9:36:35 AM] : Detecting dependent assembly Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil using Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,
processorArchitecture=msil.
* [10/15/2014 9:36:35 AM] : Detecting dependent assembly System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089,
processorArchitecture=msil.
* [10/15/2014 9:36:35 AM] : Request of trust and detection of platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [10/15/2014 9:36:43 AM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
  - File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
   at System.Deployment.Application.ComponentVerifier.VerifyComponents()
   at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification
notification, DownloadOptions options)
   at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
   at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Hi DMcGarveyt,
This is an known issue in SSRS 2008 R2 SP3. For this issue, Microsoft has published an article addressing this issue. It is not planning to release a fix for this defect. But there's workarounds for this issue. Please refer to the link below:
Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Database size would exceed your licensed limit of 10240 MB per database in ms sql 2008 r2 standard editon

Hello there,
Pl. provide solution on this on urgent if possible
REATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
I have installed MS SQL 2008 R2 Standard Edition
Error getting while restoring sql db 11gb backup file
Yogi

Hi,
Please post output of query provided by Olaf. I guess you have connected to Express edition( 2008 r2/2012/2014) and since database has limitation of 10 G hence you got this message. Please double check
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

Linked server issue using SQLNCLI versions on SQL 2008 & 2014

Hi all,
Our product creates databases on a sql server 2008 instance and creates linked servers between them to use distributed queries.
This looks like: "EXEC sp_addlinkedserver 'linkDatabaseA', '', 'SQLNCLI10', '.', NULL, NULL, 'DatabaseA'"".
Distributed queries from second database to DatabaseA work fine in this scenario.
As we want to support both SQL 2008 and SQL 2014 in the next product version, I changed this to SQLNCLI11 as the provider
and tested on SQL 2008 after installation of the SQLNCLI11 driver.
This resulted in following error message:
Msg 468, Level 16, State 9, Line 7
Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
This is very suprising as the SQL Server 2008 instance and both DB's have "SQL_Latin1_General_CP1_CI_AS" as their collation sequence.
Then I tried the opposite, installing SQLNCLI10 on SQL 2014. This gave exactly same error! Using SQLNCLI11 went fine ofcourse.
Generation sp_addlinkedserver statements with correct driver based on SQL version, I'd rather not do (some of the calls are
generated in SQL from settings in other db tables which are also used for external connx) and adding COLLATE to the queries also
has consequences like performance degradation. Adding collate on SQL 2014 with SQLNCLI10 as linked server provider results in
following error:
Msg 7399, Level 16, State 1, Line 1617
The OLE DB provider "SQLNCLI10" for linked server "linkDatabaseA" reported an error. Access denied.
Msg 7301, Level 16, State 2, Line 1617
Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "SQLNCLI10" for linked server "linkDatabaseA".
Q: Is there any way that SQLNCLI11 can be made to work for linked servers on SQL2008 (preferred solution) or SQLNCLI10 on SQL2014?
Thx for any feedback.
Regards, Jouke

Hi Sofiya,
Thx for replying.
For the deployment reasons mentioned above, I would prefer to use only one SQLNCLI version in both 2008R2 & 2012/2014 scenario's. Most preferred would ofcourse be SQLNCLI11 as this is the latest.
This would mean that I'd like to be able to configure linked server in SQL2008R2 using SQLNCLI11 driver.
I would expect that it would be downward compatible with SQLNCLI10 for all client usage, including linked server, which in essence is one SQL DB doing client access to another SQL DB either on same server instance or another. I suspect it requests DB
metadata from remote DB in order to make decisions and this seems not to work in my setup. If this metadata API is part of the public API, this could indicate that medadata API has been broken in SQLNCLI11 (heavy speculation on my part here!), which could
also affect other usage (eg. linked server between SQL2008(R2) and SQL2012/2014 instances, (I'll try to set this up and test this, might take a few days. If someone is volunteering, below are db table schemes and query, update @datasrc to point to remote sql
server instance)).
Regards, Jouke
-- This script to run on SQL2008(R2). On SQL2012/2014, install SQLNCLI10 and change @provider in sp_addlinkedserver call.
-- Pre:
-- - DatabaseA and DatabaseB are created manually in SSMS
-- - SQLNCLI11 has been installed
USE [DatabaseA]
GO
CREATE TABLE [dbo].[DatabaseATable](
[IdField] [int] NOT NULL,
[LinkField] [nchar](10) NULL,
CONSTRAINT [PK_DatabaseATable] PRIMARY KEY CLUSTERED
[IdField] ASC
) ON [PRIMARY]
GO
EXEC master.dbo.sp_addlinkedserver @server = N'linkDatabaseA', @srvproduct=N'',@provider=N'SQLNCLI11', @datasrc=N'.', @catalog=N'DatabaseA'
GO
USE [DatabaseB]
GO
CREATE TABLE [dbo].[DatabaseBTable](
[IdField] [int] NOT NULL,
[LinkField] [nchar](10) NULL,
CONSTRAINT [PK_DatabaseBTable] PRIMARY KEY CLUSTERED
[IdField] ASC
) ON [PRIMARY]
GO
SELECT b.*, a.*
FROM DatabaseBTable AS b WITH(NOLOCK)
JOIN linkDatabaseA.DatabaseA.dbo.DatabaseATable AS a
ON a.LinkField = b.LinkField
Hi Jouke Numan,
According to your description, I install SQL Native Client 11.0 OLE DB Provider in SQL Server 2008R2, and as you post, create two database on the same instance with collation in server default, then create Linked Server with SQLNCI11.0.
When I run the query statement, it can execute well. It also do not occur the collation conflict. I still recommend you check the collation of server, database, or column and so on.
SQL Server Native Client 11.0 provides OLE DB support to applications connecting to SQL Server versions 2005, 2008, 2008R2, 2012. So for the deployment reasons, you can choose the only SQLNCLI11.0 in both SQL Server 2008R2 and SQL Server 2012/2014.
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL 2014 License mapping with physical cores during/after installation

Hi,
I have ESX Machine with 24 cores. I have to purchase SQL Server 2014 Enterprise physical core based license for 24 cores. so my question is- how SQL 2014 License will mapping/hosted/linked with physical cores during/after installation on ESX machine?
Please help!!

You are most welcome Satendra :-)
Please close the thread, by marking the answer/s (the link under each response) and you can vote for responses as well (the link in the left of the response)
Ronen Ariely
[Personal Site] [Blog] [Facebook]

KB for Reporting Services and IE11 on SQL 2008 R2

We are beginning our IE 11 deployment, and we have identified that the CM reporting services site will only render certain reports when you click the 'Enterprise Mode' option.
This is a known issue addressed by http://support2.microsoft.com/kb/2917531 for SQL 2012, but I cannot find any correlating SQL 2008 R2 patch.
Can someone point me in the right direction?
Will

What version of SQL do you have installed? Is there any chance you have enterprise mode enabled by default, or for your reporting site?
Will
I'm behind your version. I'm base SP2 with the MS14-044 patch (10.50.4033). And no, I don't have enterprise mode enabled.
I've been meaning to apply SP3, I'll see if there's a difference.
Don't retire TechNet! -
(Don't give up yet - 13,225+ strong and growing)

MS SQL 2008 R2 Named instance: Login failed. Microsoft SQL server, Error: 18452) - Tryig to access using the FQDN assigned for the backup network card.

Hi,
I have a windows 2008 R2 Enterprise servers with standalone MS-SQL 2008 R2 named instance. The server is having two networks, once production and the second for backup. The server FQDN is resolving to the production IP. The backup NIC
DNS dynamic update is disabled and an "A" record is registered with the dns. While trying to connect to the instance using the management studio:
Successfuly able to connect using the instance name, the production hostname, production IP and backup IP.
but while trying to connect to the insance using the backup hostname getting the below error:
"Login failed. The login is an untrusted domain and cannot be used with windows authentication. (Microsoft SQL server, Error: 18452) "
This is required for the backup tool to get connected using the backup FQDN of the server.
Should I need to create a host name alias, request you to kindly assist me with the best recommedation to fix this.
http://blogs.msdn.com/b/dbrowne/archive/2012/05/21/how-to-add-a-hostname-alias-for-a-sql-server-instance.aspx

Hi,
It might be a kerberos issue. Check that there are valid SPN's registered using the setspn utility - http://technet.microsoft.com/en-us/library/cc731241.aspx
Thanks, Andrew
My blog...

SQL 2008 R2 Best Practices for Updating Statistics for a 1.5 TB VLDB

We currently have a ~1.5 TB VLDB (SQL 2008 R2) that services both OLTP and DSS workloads pretty much on a 24x7x365 basis. For many years we have been updating statistics (full scan- 100% sample size) for this VLDB once a week on the weekend, which
is currently taking up to 30 hours to complete.
Somewhat recently we have been experiencing intermitent issues while statistics are being updated, which I doubt is just a coincidence. I'd like to understand exactly why the process of updating statistics can cause these issues (timeouts/errors). My theory
is that the optimizer is forced to choose an inferior execution plan while the needed statistics are in "limbo" (stuck between the "old" and the "new"), but that is again just a theory. I'm somewhat surprised that the "old" statistics couldn't continue to
get used while the new/current statistics are being generated (like the process for rebuilding indexes online), but I don't know all the facts behind this mechanism yet so that may not even apply here.
I understand that we have the option of reducing the sample percentage/size for updating statistics, which is currently set at 100% (full scan). Reducing the sample percentage/size for updating statistics will reduce the total processing time, but
it's also my understanding that doing so will leave the optimizer with less than optimal statistics for choosing the best execution plans. This seems to be a classic case of not being able to have one’s cake and eat it too.
So in a nutshell I'm looking to fully understand why the process of updating statistics can cause access issues and I'm also looking for best practices in general for updating statistics of such a VLDB. Thanks in advance.
Bill Thacker

I'm with you. Yikes is exactly right with regard to suspending all index optimizations for so long. I'll probably start a separate forum thread about that in the near future, but for now lets stick to the best practices for updating statistics.
I'm a little disappointed that multiple people haven't already chimed in about this and offered up some viable solutions. Like I said previously, I can't be the first person in need of such a thing. This database has 552 tables with a whole lot more statistics
objects than that associated with those tables. The metadata has to be there for determining which statistics objects can go (not utilized much if at all so delete them- also produce an actual script to delete the useless ones identified) and what
the proper sample percentage/size should be for updating the remaining, utilized statistics (again, also produce a script that can be used for executing the appropriate update statistics commands for each table based on cardinality).
The above solution would be much more ideal IMO than just issuing a single update statistics command that samples the same percentage/size for every table (e.g. 10%). That's what we're doing today at 100% (full scan).
Come on SQL Server Community. Show me some love :)
Bill Thacker

SQL Server Licensing For EPM

If using SQL Server as your relational database to support your Oracle EPM environment and SQL Server is not licensed "Per-Processor". Do each of your Planning\Essbase users need a SQL Server CAL or do you just need one for the account being used to access the repository?

Based on my understanding (and you should speak with Microsoft directly) is anyone that is an end user of the solution needs to have a CAL and/or SQL needs to be CPU licensed. This is also how Oracle treats Essbase with third party software which may only use one batch user id -- you wouldn't be able to license one Essbase user and then have 3000 users coming off of a third party solution.
At the end of the day the CPU licensing for SQL server will make the most sense unless you have a really really small environment.
Regards,
John A. Booth
http://www.metavero.com

JDBC 1.2 for SQL 2008

Hi Gurus,
I searched in SAP Marketplace and saw that the JDBC adapter 1.2 posted there is for SQL 2005 server only. May I know where I can download a JDBC 1.2 adapter for the 2008 SQL server? I'm working with XI 7.0.
Thanks all.
Regards,
SAPenthusiast

Hello,
Check these notes:
Note 639702 - JDBC Driver for Microsoft SQL Server
Note 1600699 - Microsoft jdbc driver 1.2 support
I think you can just use the JDBC 1.2 that appears for download in SQL Server 2005. Check http://msdn.microsoft.com/en-us/sqlserver/aa937724 for example. The same driver is used to connect different DB versions.
Cheers,
Diego.

Upgrade MS SQL 2005 to MS SQL 2008 (R2) for High-Availability SAP ERP System

Hi,
We are having ECC 6.0 SR3 Hight-Availability system on windows cluster environment.
Our platform is Windows Server 2008 SR2 with MS SQL Server 2005 SR3. We have two nodes in our windows cluster. Active-passive nodes.
Node-1 is having CI, ASCS, ERS & DATABASE
Node-2 is having DI, ERS & stand-by database software.
I've check all the pre-requisites for sql upgrade.
our kernel is on 700_Rel. I'm planning to stabilize the kernel with 721_Rel before Database upgrade.
Support package patch level condition is met for sql upgrade in our scenario.
Now we are planning to upgrade our MS SQL Server from 2005 sr3 to MS SQL Server 2008r2.
Please provide me the steps for Kernel upgrade and sql upgrade to 2008r2 on Windows cluster environment.
Thanks
Venkat

Hi Venkat
1. Could you share your ECC support package level & also you can check the PAM
2. Yes you can upgrade the MS Sql to 2008 R2, before starting upgrade Kindly ensure the full OS / DB level backup on both cluster node's
3. MS Sql 2008 R2 upgrade refer the SAP Note
1152240 - Setting Up Microsoft SQL Server 2008 (R2)
4. For Kernel upgrade its release change kindly go thru the SAP Notes
1713986 - Installation of kernel 721 (EXT)
1728283 - SAP Kernel 721: General Information
1726899 - 721 DCK: Upgrade from 7.0n to 7.1n
BR
SS

BPC 7.5 SP4 Support for Windows 2008 R2 and SQL 2008 R2

The release notes for BPC 7.5M SP04 state that support has been added for both Windows 2008 R2 and SQL 2008 R2.
For SQL 2008 R2, there is nothing in the feature pack described as "SQL 2005 Backward Compatibility Components" - which was a required piece for BPC 7/7.5 on SQL 2008. Is the SQL 2008 version still a requirement, or does BPC 7.5 now not need the Backward Compatibility components?
Also, the ReprotViewer executable that is packaged with BPC 7.5 is the one for SQL 2008- will that work when installing SQL 2008 R2?
thanks,
Tony DeStefanis
Column5 Consulting

Hi,
we have the same environment (BPC 7.5 SP4 on Windows 2008 R2 64 bit and SQL Server 2008 R2 64bit).
we are developping our application-set and for the moment we have no problem.
regards
massimo

SQL 2014 license for SQL 2008

Similar Messages

Maybe you are looking for