Hi,

I need SQL Server 2016 SP2 CU2 and not CU3 but I cannot find this version anymore, everything routes me back to CU3.

I nned CU2 as this is what we have tested against and not CU3, and we don't have time to test CU3 before we go live.

thanks

Hello,

I have recently installed SQL Server 2017 Enterprise Developer Edition for evaluation and am particularly interested in all aspects of security.  So for the install, I have checked to install SSIS Scale Out Master and SSIS Scale Out Worker.  I accepted the default virtual service accounts for these two services as well as for others (ie sql server, sql server agent).  I configured SQL Server login audit events to write the Windows Event -> Application Log.   I keep seeing entries like in Windows Event Viewer:

Login failed for user 'NT Service\SSISScaleOutMaster140'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]

I then checked the Local Users & Groups on the SQL Server machine and I didn't see this account - 'NT Service\SSISScaleOutMaster140' or any other service accounts (like sql server service, agent and etc..) which I had accepted as defaults during the installation.

Questions are:

Q1 - Where do I find these virtual accounts - NT Service\*

Q2 - What's the reason for the login failure related to 'NT Service\SSISScaleOutMaster140' and how do I fix this?

Thank you

Hello,

  When I right click on 'Databases' on a SQL server, the  'Attach Databases' opens with disabled content. Hence I am unable to proceed with attaching any databases.

Please have a look.



Hello,

Since two months I can see many entries with the below sentences in SQL logs.

2017-04-24 22:01:43.900 spid31s      SSBDT: Dialog timer delete during registration (did: 725D87C0-8AAF-4383-BCFC-725AC025CD1D:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:02:41.290 spid31s      SSBDT: Dialog timer delete during registration (did: 6F5BF516-934A-45E4-B1B1-D60DF3401B4E:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:03:17.650 spid31s      SSBDT: Dialog timer delete during registration (did: F044EE94-7203-4FF5-9BB6-00D21B86E686:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:03:22.350 spid31s      SSBDT: Dialog timer delete during registration (did: 0B92D137-915C-4920-9C69-541F87266D90:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:03:37.980 spid31s      SSBDT: Dialog timer delete during registration (did: 958A51D1-B18F-410F-93B5-358D10C81EF5:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:03:40.310 spid31s      SSBDT: Dialog timer delete during registration (did: 14373439-9330-4E2C-BF2B-6901A3ED42BF:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:07:39.000 spid31s      SSBDT: Dialog timer delete during registration (did: 6E9C57B7-BDD5-42BC-BA9A-A5A3F97DC91A:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:08:02.360 spid31s      SSBDT: Dialog timer delete during registration (did: 98B47642-1373-4EF7-86B0-E320B48611A9:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:08:02.480 spid31s      SSBDT: Dialog timer delete during registration (did: 1D1263CE-151D-4C64-90BA-4293A29D6BD0:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:09:27.750 spid31s      SSBDT: Dialog timer delete during registration (did: C7D98CCF-F67D-450B-870B-0242585E9B07:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:09:36.700 spid31s      SSBDT: Dialog timer delete during registration (did: 0D243BC3-6B83-45A0-AF2B-E4AF24098B9D:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:09:51.270 spid31s      SSBDT: Dialog timer delete during registration (did: 4CCDA7EA-FB1E-44C7-9234-C0D7C8484750:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:10:15.450 spid31s      SSBDT: Dialog timer delete during registration (did: 2A515B80-9AFA-45F2-9ECB-1328BBB63852:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:11:10.770 spid31s      SSBDT: Dialog timer delete during registration (did: 9920B4CC-EF38-4A8C-A3AE-FAADD7D75267:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:11:15.610 spid31s      SSBDT: Dialog timer delete during registration (did: 4ABA0501-7CD2-4F58-9B59-49A7A9799092:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:11:20.960 spid31s      SSBDT: Dialog timer delete during dispatch (did: 8FAECCF7-6AC5-4FB2-84DC-4927E839D028:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:13:24.770 spid31s      SSBDT: Dialog timer delete during registration (did: A932AF41-C0D0-4234-899B-5E5A4565F924:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:13:24.910 spid31s      SSBDT: Dialog timer delete during registration (did: 00F178A3-640D-44E4-9C39-A69271B279C9:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:13:42.310 spid31s      SSBDT: Dialog timer delete during dispatch (did: 20D9F06E-BC29-4BA5-9623-E08765B42BC7:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:14:00.290 spid31s      SSBDT: Dialog timer delete during registration (did: AA47FA4F-F793-4D89-BBCB-2E434596476F:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:16:31.660 spid31s      SSBDT: Dialog timer delete during registration (did: DD35C46C-7EF0-410F-B78D-CB38DFBD4DEB:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:17:06.290 spid31s      SSBDT: Dialog timer delete during registration (did: E857E323-ED31-4FEC-9AB9-39115D50CA4E:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:18:47.130 spid31s      SSBDT: Dialog timer delete during registration (did: CEDC4256-B4F2-4844-B2DA-9F49C41DE529:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:19:06.390 spid31s      SSBDT: Dialog timer delete during registration (did: 2ACDA3E2-4449-46A8-8A64-E8DF072FEF2A:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:21:30.410 spid31s      SSBDT: Dialog timer delete during dispatch (did: E09596A9-CD56-4597-B428-DE392D542E29:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:22:32.890 spid31s      SSBDT: Dialog timer delete during dispatch (did: EC39EEE2-ACC5-49F4-A375-2CC3EA2C68CD:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:23:01.630 spid31s      SSBDT: Dialog timer delete during dispatch (did: DF7D37D2-C4C6-403B-AD77-EC070EC47F36:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:23:25.520 spid31s      SSBDT: Dialog timer delete during dispatch (did: 8FDB1B72-8C0B-49F3-B305-93DC9F52EC72:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:25:22.860 spid31s      SSBDT: Dialog timer delete during dispatch (did: 8E7E1C64-16C7-4BB9-A77C-717B1BDF5859:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:25:45.920 spid31s      SSBDT: Dialog timer delete during dispatch (did: E47E8924-8741-48B0-BB55-2B573247CEE7:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:27:17.560 spid31s      SSBDT: Dialog timer delete during dispatch (did: CBE4F1C7-A98D-424E-AD0D-339727F76937:Target, OpType: DialogCleanupDispatch OpResult: Null)

We are using SQL server 2012 SP3

Do you know what could be the source of that problem?

We could not find info....

Hi there,

We had bought Volume License for our client for their SQL server for 50 units.

And we had received Volume License certificate from our provider

And (the accounting vendor) had install it in the server last year, around July 2017.

Last week Monday, the client, called us and told us that their SQL server stop functioning, then i've try to remote into their server and found that their SQL services not running - even though i try to restart the services and reboot the whole server.

Upon something is fishy, i went down to Event Logs to inspect, and to my shock, the logs reported, the SQL services could not be started due to the expiry of the SQL Trial version. Then i checked the SQL version, yes, it is evaluation version and asked to enter the product keys.

My question is, i had log into the VLSC and downloaded the correct SQL server 2016 version and put it into that server to be installed. Then how come after a year, (evaluation is 180 days or 6 months), this SQL version suddenly changed to Evaluation version. Anyone had any ideas about this ?

And as far as i know Volume Licensing product does not have Product Key - as i could not see any product key in VLSC when i downloaded the SQL server 2016.

I'm trying to run a silent install of SQL Server 2014 and getting the error: Media ScenarioEngine.exe returned exit code: 0x84B40001. I call this install from a C# program but if I run the same command from a command line it works fine. Here's the command I'm issuing:

SQLExpr_x64_ENU.exe /SkipInstallerRunCheck /QUIETSIMPLE /SAPWD="OurPWHere" /INSTANCENAME="PACSGEAR" /INSTANCEID="PACSGEAR" /ACTION=Install /FEATURES=SQLENGINE /AGTSVCSTARTUPTYPE=Manual /ISSVCSTARTUPTYPE=Automatic /ISSVCACCOUNT="NT AUTHORITY\NetworkService" /ASSVCSTARTUPTYPE=Automatic /SQLSVCSTARTUPTYPE=Automatic /SQLSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /SQLSYSADMINACCOUNTS="BUILTIN\Administrators" /SECURITYMODE=SQL /IACCEPTSQLSERVERLICENSETERMS /SKIPRULES=RebootRequiredCheck

And here's a snippet of the c# code that fails

string commandLine = "/SkipInstallerRunCheck /QS /SAPWD=" + sSQLOurSAPwd + " " +
                "/INSTANCENAME=" + sqlInstance + " /INSTANCEID=" + sqlInstance + " /ACTION=Install " +
                "/FEATURES=SQLENGINE /AGTSVCSTARTUPTYPE=Manual /ISSVCSTARTUPTYPE=Automatic " +
                "/ISSVCACCOUNT=\"NT AUTHORITY\\NetworkService\" /ASSVCSTARTUPTYPE=Automatic /SQLSVCSTARTUPTYPE=Automatic " +
                "/SQLSVCACCOUNT=\"NT AUTHORITY\\NETWORK SERVICE\" /SQLSYSADMINACCOUNTS=\"BUILTIN\\Administrators\" /SECURITYMODE=SQL " +
                "/IACCEPTSQLSERVERLICENSETERMS /SKIPRULES=RebootRequiredCheck";

Process installerProcess = Process.Start(sSQLSetup, commandLine);

I've googled the exact error message and found nothing. Please help!

Hi all,

We're looking to implement a SQL 2016 server (Standard) with multiple DB's within the same instance.

One of the apps we're putting in to it is SolarWinds which is very hungry.

Is there any way to prevent that from impacting the other apps running out of this instance within the SQL standard license?

I know with Ent you get access to resource governor but is there anything similar in Standard? Or should we just be looking at separate instance / clusters?

Thanks,

Tom

Hello,

Trying to deploy SQL Server 2016 on a maschine that already has SQL Server Mgmt Studio 2017 (v14.0.17277.0) installed. This leads to an exception during installation: 

(01) 2018-10-12 13:25:04 Slp: Target package: "C:\WINDOWS\ccmcache\n\1033_ENU_LP\x64\setup\x86\DACFramework.msi"
(01) 2018-10-12 13:25:04 Slp: MSI Error: 0 A newer version of Microsoft SQL Server Data-Tier Application Framework is already installed.
(01) 2018-10-12 13:25:04 Slp: InstallPackage: MsiInstallProduct returned the result code 1603.

Indeed, the machine has SQL Server Data-Tier Application Framework x86 v14.0.4079.2 already installed during setup of SSMS 2017.

Reproduced this by: 

• uninstalling SSMS 2017
• uninstalling Data-Tier Application Framework
• rebooting
• installing SSMS 2017 again
• > this brings back the data tier application framework v14

When I uninstall the framework and then retry setup for SQL Server 2016, the installation completes successfully.

This creates the following questions for me: 

• is it generally not supported to install SQL Server 2016 when SSMS 2017 is already installed?
• can I somehow prevent SSMS 2017 from installing Data Tier Application Framework?
• can I tell SQL Server 2016 to ignore teh fact that a newer version of Data Tier Application Framework is already installed?

im go to take adhoc sql full backup, before application upgrade eg: BACKUP DATABASE testdb  TO DISK = 'C:\testdb.BAK' WITH STATS, DESCRIPTION = 'Full backup for AdventureWorks' GO how do you I know, my backup is not corrupted, and will work after repair sql database, incase if required Sorry I dont have environment to test.. it.. Do i need to do consistency check or readability check before take backup, if yes, how can i do that in Tsql?

Hi,

One guy had ordered a server with OS and SQL. Due to some process failure, he lacked SQL server license, so he installed evaluate version of SQL 2016 upon project deployment. Then -as a delivery correction- he received the OEM license for SQL but it has a different license key than required for Eval activation. Can we expect kind of product/key exchange from Microsoft?

If not, does he have to perform kind of Clean Reinstallation, or simple reinstallation could solve his issue?

I'm trying to install Microsoft SQL Server 2016 Developer edition on my home computer for educational purposes. At first, the Database Engine Services would not install. Five days later, I've tried much to no avail, including the instructions found in:

http://social.technet.microsoft.com/wiki/contents/articles/24364.sql-server-troubleshooting-could-not-find-database-engine-startup-handle-error-during-installation.aspx

Following multiple installs/uninstalls, and now a registry key deletion, I've gotten various errors including (1) "Wait on the Database Engine recovery handle failed", and (2) "Object reference not set to an instance of an object."

How much more of this before I must go onto suicide watch? Any help is appreciated.

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2147467261
  Start time:                    2016-11-23 04:30:07
  End time:                      2016-11-23 04:41:17
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


Machine Properties:
  Machine name:                  XPS
  Machine processor count:       4
  OS version:                    Microsoft Windows 10 Home (10.0.14393)
  OS service pack:               
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured
  SQL Server 2016                                                          SSMS                                     1033                                      13.0.16000.28   No         Yes       
  SQL Server 2016                                                          Adv_SSMS                                 1033                                      13.0.16000.28   No         Yes       

Package properties:
  Description:                   Microsoft SQL Server 2016 
  ProductName:                   SQL Server 2016
  Type:                          RTM
  Version:                       13
  Installation location:         E:\x64\setup\
  Installation edition:          Developer

  Slipstream:                    True
  SP Level                       1

Product Update Status:
  Success: KB 3182545

Product Updates Selected for Installation:
  Title:                         Microsoft SQL Server 2016  with SP1
  Knowledge Based Article:       KB 3182545
  Version:                       13.1.4001.0
  Architecture:                  x64
  Language:                      1033

  Update Source:                 Slipstream


User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTELSVCACCT:                  <empty>
  ASTELSVCPASSWORD:              <empty>
  ASTELSVCSTARTUPTYPE:           0
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Automatic
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161123_042941\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    false
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE, CONN
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTROPENLICENSETERMS:      false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  ISTELSVCACCT:                  <empty>
  ISTELSVCPASSWORD:              <empty>
  ISTELSVCSTARTUPTYPE:           0
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  MRCACHEDIRECTORY:              
  NPENABLED:                     0
  PBDMSSVCACCOUNT:               <empty>
  PBDMSSVCPASSWORD:              <empty>
  PBDMSSVCSTARTUPTYPE:           0
  PBENGSVCACCOUNT:               <empty>
  PBENGSVCPASSWORD:              <empty>
  PBENGSVCSTARTUPTYPE:           0
  PBPORTRANGE:                   <empty>
  PBSCALEOUT:                    false
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
  SQLSVCINSTANTFILEINIT:         false
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           XPS\Joseph
  SQLTELSVCACCT:                 NT Service\SQLTELEMETRY
  SQLTELSVCPASSWORD:             <empty>
  SQLTELSVCSTARTUPTYPE:          Automatic
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBFILECOUNT:            4
  SQLTEMPDBFILEGROWTH:           64
  SQLTEMPDBFILESIZE:             8
  SQLTEMPDBLOGDIR:               <empty>
  SQLTEMPDBLOGFILEGROWTH:        64
  SQLTEMPDBLOGFILESIZE:          8
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  TCPENABLED:                    0
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  Slipstream
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161123_042941\ConfigurationFile.ini

Detailed results:
  Feature:                       Client Tools Connectivity
  Status:                        Passed

  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          -2147467261
  Error description:             Object reference not set to an instance of an object.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0x9C8C9C81%400x44A889F9&EvtType=0x9C8C9C81%400x44A889F9

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       SQL Client Connectivity
  Status:                        Passed

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161123_042941\SystemConfigurationCheck_Report.htm

Cannot install SQL 2016 correctly.

When the installation is almost done it will have a dialog  box saying "Object references not set to an instance of an object".

Then when the installation finished, it says some feature failed, one of which is Database Service Engine.

And once I tried connecting to the database engine I could not login with my windows authentication or the SQL server authentication for SA user, But I can connect to the analysis server.

Then Configuration manages doe not show the SQL services, it says "MMC could not create the snap-in. The snap-in might not have been installed correctly."

My machine is a Windows 10.

Apologies as I still can't upload images or URLs as my account is still to be verified,

Please help.

I'm running windows 8.1, SSMS 17 and Visual Studio 2017 CE. When I open SSMS and either connect to a server or click cancel in the opening dialog box I get an error that my license for Visual Studio has expired. When I click close on the error dialog, SSMS exits. Visual Studio runs fine on it's own. Anyone have an idea how to fix this?

I tried installing sql server 2017 but I gpt some errors ....by the way I am using visual stdio 2017..

this is the error message :


PerfLib 2.0 counter removal failed with exit code 2. Command line: C:\WINDOWS\system32\unlodctr.exe /m:hkengperfctr.xml from directory C:\Program Files\Microsoft SQL Server\140\Shared\.

this is the log summary :

Please clarify.

I now support SQL Servers installed in USA, UK and Poland.  I'm in the US.  All SQLs are "English" language installs.  For SERVICE PACK / CUs / etc., are there COUNTRY SPECIFIC downloads (UK, Poland) or do I just stick to "English" language?

Hi,

I have SQL Server Cluster running with two sql intances. SQL server 2008 r2 and Sql server 2012 r2 and current version is

SQL SERVER 2012 r2

Microsoft SQL Server Management Studio11.0.5058.0
Microsoft Analysis Services Client Tools11.0.5058.0

SQL SERVER 2008 r2

What is the best practice to upgrade the Cluster SQL CU?

Regards,

Mohammed

Please remember to mark the replies as answers if they helped. Br, Farhan

Please help,

We downloaded SQL 2014 Enterprise edition evaluation version.

We now want to officially license the product.

My server has 10 cores.

We ordered license packs to meet the per core licensing requirement.

We found a Product ID code off a forum which converted the evaluation version to licensed version.

Question: How do we apply the additional (per core) licenses to the product?

Or do I not apply them and just retain for auditing purposes ?