Licensing of a Test SQL Server

Hi,
My question is regarding the use of SQL in a Development Environment. We have a VL Agreement. We have a Historical server using SQL in a 2 server cluster with a SAN. We purchased a SQL 2012 Standard Server for each server plus CAL's for all devices
and users. For testing, a single server with local storage is used to develop and test changes before changing the production cluster. We have 2 Developers that will use the test server and 2 Developer Licenses were purchased. We used the production version
of the SQL media to create the test server instead of the Dev version of the media. Are we compliant?

Hi RonAtSE,
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
Lydia Zhang
TechNet Community Support

Similar Messages

  • How to tell whether a license used to install SQL Server is MSDN license or Volume license?

    I want to check license used to install SQL Server is MSDN license or Volume license for SQL Servers which are at least SQL Server 2008 on Windows 2008 R2.  Is there any script/command/tool that I can run on Windows or SQL Server to find such
    information? 

    Hello,
    This is a community forum for technical questions & issues.
    For question regarding pricing / licensing please contact a Microsoft sales partner or licensing expert.
    Call (1-800-426-9400), Monday through Friday, 6:00 AM to 6:00 PM PST to speak directly to Microsoft licensing specialist.
    http://www.microsoft.com/en-us/server-cloud/products/sql-server/buy.aspx
    T-SQL Articles
    T-SQL e-book by TechNet Wiki Community
    T-SQL blog

  • SQL Server evaluation license expired

    I have a discovery system I installed in Feb 2007. Due to other work we've not used the system in a while. I'm resurrecting it and the SQL evaluation license has expired. In reading thru the forum, it's suggested that tiy detach the databases, uninstall the eval and install a licensed copy. Since SQL server qon't start, how do you detach the databases?

    I've Installed a licensed SQL Server, attached the databases and am getting an error when I try to log in:
    DBCHECK Wrong Server collation perfroms SQL2005 after upgrade steps Please see note 126973
    Before I completely hose things up is there something I mssed when I installed the SQL Server?

  • Which SQL server edition do I need? Developer or Standard?

    I currently work for a large firm using SQL Server 2012 with Management Studio - I use this to connect to our database and run querys against. I also use Visual Studio 2013 to create .rdlc report files.
    I need to replicate what I'm doing for the large firm, but on a much smaller scale. All I need to be able to do is restore a database to a SQL Server that is anywhere between 10-20GB in size, use SQL Management Studio to run queries against that restored
    database, and create the same type of reports I am creating using Visual Studio 2013 (.rdlc files).
    I think because the database to restore is larger than 10GB I can't get away with the express edition. Can I just use the Developer edition? Or do I need the standard edition?
    thanks in advance.

    Development edition licenses can be used to install anything that isn't production, provided that everyone that connects to the server has their
    own development license. MSDN licenses can be used as well if everyone has an MSDN license.
    http://sqlmag.com/sql-server-2014/sql-server-2014-developer-edition-licensing
    If you are going to do some test you are ok with developer edition otherwise you need to go for standard edition.

  • Temporarily disable Digital Signature Checks to Install MS SQL Server 2008 with no Internet Access

    I am attempting to install a licensed copy of MS SQL Server 2008 in a Private Enclave that does NOT have Internet access on a Win2008 R2 SP1 server (that is VM - thus I can't reboot and press F8 to select "Disable Driver Signature Enforcement"
    ). The installation fails with an error of the vc_red.cab file being found either corrupt or a bad digital signature.  The file is good, but the signature has an expiration of 2011.   I understand that a DOTNET SDK v1.1 program called setreg.exe
    will enable disabling the digital signature check, but I am not permitted to use that program. 
    I might be permitted to use the "Signtool.exe" utility, but it is not clear what command sequences are necessary to disable and then re-enable the Digital Signature checks.
    I saw a thread that recommended using the command:
    bcdedit.exe /set nointegritychecks ON
    However, the comments indicated that this might not have worked.
    Are there Registry settings I can use with regedit to make the necessary changes to be able to install the application?  I anticipate running into this problem with other software when I do not have Internet connectivity.   I already tried
    downloading the Microsoft CRL files; updated the lists on the Server; and rebooted.  This did not solve my problem.  

    Hi,
    As far as I know, it is not recommended to disable digital signature check.
    Since we are not familair with installing MS SQL server, please also refer to SQL forums below to see if experts there have more insights regarding the matter.
    https://social.technet.microsoft.com/Forums/sqlserver/en-US/home
    Best Regards,
    Amy
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Commercial distributed application with SQL Server 2008 back-end

    Hi All, I am suffering some confusion and wondered if anyone could clear up a few questions for me.
    I am currently developing an application to be sold commercially, to be deployed locally on a customer's site. It is a client-server application and the server utilises an SQL Server 2008 back-end. Client applications however do connect directly to the SQL
    Server.
    We probably want to support about 100+ client applications. Each client application could feasibly be making several SQL query requests per second.
    Firstly, what are the licensing implications of this for the customer? I understand SQL Server 2008 can support 30000+ concurrent connections, but am I correct in thinking that each client application will require CALs? Or I understand there is a "processor
    licence"...
    Secondly, and I know this is quite a broad question, but can anyone offer a rough estimation of the processing/storage requirements for the server?
    Thanks in advance!

    Hi click,
    Usually, SQL Server is licensed through Microsoft Volume Licensing programs using two software licensing models, one is the Per Processor (Core-based) licensing model, another is Server plus Client Access License (Server+CAL) licensing model which is based
    on the users or devices accessing the product.
    Using the Per Core Licensing Model When running SQL Server in a physical operating system environment (OSE), all physical cores on the server must be licensed. When licensing SQL Server software under the Server+CAL model, customers purchase a server license
    for each server and a client access license (CAL) for each device (Device CAL) and/or user (User CAL) accessing SQL Server or any of its components.
    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,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Installation Error for SQL Server 2008 R2 on windows vista

    2014-09-20 07:49:26 Slp: ----------------------------------------
    2014-09-20 07:49:26 Slp: Setting: TIMESTAMP
    2014-09-20 07:49:26 Slp: Value specified: 20140920_074907
    2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
    2014-09-20 07:49:26 Slp: ----------------------------------------
    2014-09-20 07:49:26 Slp: Setting: LOGMARKER
    2014-09-20 07:49:26 Slp: Value specified: _ComponentUpdate
    2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
    2014-09-20 07:49:26 Slp: ----------------------------------------
    2014-09-20 07:49:26 Slp: Setting: INSTALLMEDIAPATH
    2014-09-20 07:49:26 Slp: Value specified: C:\Downloaded\SQL Server 2008\x86\setup\
    2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
    2014-09-20 07:49:26 Slp: ----------------------------------------
    2014-09-20 07:49:26 Slp: Setting: MEDIALAYOUT
    2014-09-20 07:49:26 Slp: Value specified: Full
    2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
    2014-09-20 07:49:26 Slp: ----------------------------------------
    2014-09-20 07:49:26 Slp: Completed Action: ProcessChainerCommandLineArguments, returned True
    2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:26 Slp: Running Action: ProcessMediaChainerConfigFileArguments
    2014-09-20 07:49:26 Slp: Completed Action: ProcessMediaChainerConfigFileArguments, returned True
    2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:26 Slp: Running Action: ProcessChainerConfigFileArguments
    2014-09-20 07:49:26 Slp: Completed Action: ProcessChainerConfigFileArguments, returned True
    2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:26 Slp: Running Action: ProcessSlipstreamParameters
    2014-09-20 07:49:26 Slp: Completed Action: ProcessSlipstreamParameters, returned True
    2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:26 Slp: Skipping Action: SetRoleAndUIModeForExpressMedia
    2014-09-20 07:49:26 Slp: Action is being skipped due to the following restrictions: 
    2014-09-20 07:49:26 Slp: Condition "IsMediaExpress" did not pass as it returned false and true was expected.
    2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:26 Slp: Running Action: ValidateChainerSetting
    2014-09-20 07:49:26 Slp: -- PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
    2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : NormalizePid found null or empty pid
    2014-09-20 07:49:26 Slp: -- PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
    2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : Initialize is initializing using input pid=[PID value hidden]
    2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : NormalizePid found null or empty pid
    2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : Initialize proceeding with normalized pid=[PID value hidden]
    2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : Initialize called ValidatePid, output is pid=[PID value hidden] validateSuccess=True output editionId=EVAL(0x2467BCA1)
    2014-09-20 07:49:27 Slp: -- PidPublicConfigObject : ValidateSettings initialized private object, result is initializeResult=Success
    2014-09-20 07:49:27 Slp: Completed Action: ValidateChainerSetting, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: ProcessFeatureCommandLineArguments
    2014-09-20 07:49:27 Slp: ----------------------------------------
    2014-09-20 07:49:27 Slp: Completed Action: ProcessFeatureCommandLineArguments, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: ProcessMediaFeatureConfigFileArguments
    2014-09-20 07:49:27 Slp: Completed Action: ProcessMediaFeatureConfigFileArguments, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: ProcessFeatureConfigFileArguments
    2014-09-20 07:49:27 Slp: Completed Action: ProcessFeatureConfigFileArguments, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: StartSqmSession
    2014-09-20 07:49:27 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-09-20 07:49:27 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
    2014-09-20 07:49:27 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
    2014-09-20 07:49:27 Slp: Completed Action: StartSqmSession, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: ValidateSettingsAgainstScenario
    2014-09-20 07:49:27 Slp: Scenario: ComponentUpdate
    2014-09-20 07:49:27 Slp: Completed Action: ValidateSettingsAgainstScenario, returned True
    2014-09-20 07:49:27 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: SetComponentUpdateScenarioFlags
    2014-09-20 07:49:27 Slp: Completed Action: SetComponentUpdateScenarioFlags, returned True
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: ExecuteInitWorkflow
    2014-09-20 07:49:27 Slp: Workflow to execute: 'INITIALIZATION'
    2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:27 Slp: Running Action: InitializeMsiExtension
    2014-09-20 07:49:29 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-09-20 07:49:29 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100\Bootstrap
    2014-09-20 07:49:29 Slp: Completed Action: InitializeMsiExtension, returned True
    2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:29 Slp: Skipping Action: InitializeConfigAction
    2014-09-20 07:49:29 Slp: Action is being skipped due to the following restrictions: 
    2014-09-20 07:49:29 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableExternalMsiConfiguration set" did not pass as it returned false and true was expected.
    2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:29 Slp: Skipping Action: RunDiscoveryAction
    2014-09-20 07:49:29 Slp: Action is being skipped due to the following restrictions: 
    2014-09-20 07:49:29 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableDiscoverableProducts set" did not pass as it returned false and true was expected.
    2014-09-20 07:49:29 Slp: Completed Action: ExecuteInitWorkflow, returned True
    2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:29 Slp: Running Action: ExecuteStartUiWorkflow
    2014-09-20 07:49:29 Slp: Workflow to execute: 'STARTUI'
    2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:29 Slp: Running Action: InstallWizard
    2014-09-20 07:49:29 Slp: Start Action: ComponentUpdate
    2014-09-20 07:49:29 Slp: Configuration file: C:\Downloaded\SQL Server 2008\x86\configuration.uicfg
    2014-09-20 07:49:30 Slp: Adding registration information 'ShowWizard' for type 'Microsoft.SqlServer.Management.ActionHandlerInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'InstallWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'InstallClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'AddNode' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'RemoveNode' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'PrepareClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'CompleteClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'UninstallWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'UpgradeWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'ComponentUpdate' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'RepairWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'RunRulesUI' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'EditionUpgradeWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'PatchWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'RemovePatchWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'PrepareImageWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: Adding registration information 'CompleteImageWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
    2014-09-20 07:49:30 Slp: -- SkuPublicConfigObject : Calling SkuPublicConfigObject.Calculate.
    2014-09-20 07:49:31 Slp: Completed Action: InstallWizard, returned True
    2014-09-20 07:49:31 Slp: ----------------------------------------------------------------------
    2014-09-20 07:49:31 Slp: Running Action: GatherUserSettings
    2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid is normalizing input pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid added dashes to pid, output pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Initialize is initializing using input pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid is normalizing input pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Initialize proceeding with normalized pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Read lcid 1033 from CultureInfo
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Pid validation of input pid '[PID value hidden]' succeeded, resulting edition is 'DATA_CENTER' channel 'OEM'
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Initialize called ValidatePid, output is pid=[PID value hidden] validateSuccess=True output editionId=DATA_CENTER(0xC5AA9665)
    2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings initialized private object, result is initializeResult=Success
    2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid is normalizing input pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid added dashes to pid, output pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
    2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings found pid=[PID value hidden] is already validated and initialized.
    2014-09-20 07:50:22 Slp: License file: C:\Downloaded\SQL Server 2008\1033_ENU_LP\x86\1033\License_DC_OEM.rtf
    2014-09-20 07:50:25 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-09-20 07:50:25 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
    2014-09-20 07:50:25 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
    2014-09-20 07:50:25 Slp: License file: C:\Downloaded\SQL Server 2008\1033_ENU_LP\x86\1033\License_DC_OEM.rtf
    2014-09-20 07:50:25 Slp: Completed Action: GatherUserSettings, returned True
    2014-09-20 07:50:25 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:25 Slp: Running Action: RegisterRetryHandler
    2014-09-20 07:50:25 Slp: Completed Action: RegisterRetryHandler, returned True
    2014-09-20 07:50:25 Slp: Completed Action: ExecuteStartUiWorkflow, returned True
    2014-09-20 07:50:25 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:25 Slp: Running Action: NotifyProgressCountDisplay
    2014-09-20 07:50:26 Slp: Completed Action: NotifyProgressCountDisplay, returned True
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Running Action: ExecuteCalculateScenarioWorkflow
    2014-09-20 07:50:26 Slp: Workflow to execute: 'CALCULATESCENARIO'
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Running Action: ClearCalculatedState
    2014-09-20 07:50:26 Slp: Completed Action: ClearCalculatedState, returned True
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Skipping Action: SetUninstallEnableInstallMatchingByInstanceId
    2014-09-20 07:50:26 Slp: Action is being skipped due to the following restrictions: 
    2014-09-20 07:50:26 Slp: Condition "Is the user's scenario set to Uninstall" did not pass as it returned false and true was expected.
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Skipping property ArgInstanceName of class: SetFeatureInstallStateAction
    2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s): 
    2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableDiscoverableProducts set" did not pass as it returned false and true was expected.
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Skipping property ArgSqlInstanceId of class: SetFeatureInstallStateAction
    2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s): 
    2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableInstallMatchingByInstanceId set" did not pass as it returned false and true was expected.
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Skipping property ArgASInstanceId of class: SetFeatureInstallStateAction
    2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s): 
    2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableInstallMatchingByInstanceId set" did not pass as it returned false and true was expected.
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Skipping property ArgRSInstanceId of class: SetFeatureInstallStateAction
    2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s): 
    2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableInstallMatchingByInstanceId set" did not pass as it returned false and true was expected.
    2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:26 Slp: Running Action: SetFeatureInstallStateAction
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_Cpu32: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_fulltext_Cpu32: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_Cpu32: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_Cpu32: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_as_spi_Cpu32: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_rs_Cpu32: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_rs_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_rs_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:27 Slp: Package ID sql_rs_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_Cpu32: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_Cpu32: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_bids_Cpu32: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_bids_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:28 Slp: Package ID sql_bids_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_Cpu32: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_Cpu32: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1028: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1031: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1033: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1036: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1040: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1041: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1042: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1046: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1049: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_2052: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_3082: NotInstalled
    2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1053: NotInstalled
    2014-09-20 07:50:29 Slp: Error: Action "Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction" threw an exception during execution.
    2014-09-20 07:50:29 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Value cannot be null.
    2014-09-20 07:50:29 Slp: Parameter name: productVersion ---> System.ArgumentNullException: Value cannot be null.
    2014-09-20 07:50:29 Slp: Parameter name: productVersion
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion(String value)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallPropertyByProductCode(PackageInstallProperty pkg, String prodCode)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallProperty(PackageInstallProperty pkg)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.ExecuteAction(String actionId)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2014-09-20 07:50:29 Slp:    --- End of inner exception stack trace ---
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
    2014-09-20 07:50:29 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
    2014-09-20 07:50:29 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Value cannot be null.
    2014-09-20 07:50:29 Slp: Parameter name: productVersion ---> System.ArgumentNullException: Value cannot be null.
    2014-09-20 07:50:29 Slp: Parameter name: productVersion
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion(String value)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallPropertyByProductCode(PackageInstallProperty pkg, String prodCode)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallProperty(PackageInstallProperty pkg)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.ExecuteAction(String actionId)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2014-09-20 07:50:29 Slp:    --- End of inner exception stack trace ---
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    2014-09-20 07:50:29 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2014-09-20 07:50:33 Slp: Received request to add the following file to Watson reporting: C:\Users\Kimi Raikkonen\AppData\Local\Temp\tmpB4ED.tmp
    2014-09-20 07:50:33 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2014-09-20 07:50:33 Slp: Inner exceptions are being indented
    2014-09-20 07:50:33 Slp: 
    2014-09-20 07:50:33 Slp: Exception type: System.ArgumentNullException
    2014-09-20 07:50:33 Slp:     Message: 
    2014-09-20 07:50:33 Slp:         Value cannot be null.
    2014-09-20 07:50:33 Slp:         Parameter name: productVersion
    2014-09-20 07:50:33 Slp:     Stack: 
    2014-09-20 07:50:33 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion(String value)
    2014-09-20 07:50:33 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallPropertyByProductCode(PackageInstallProperty pkg, String prodCode)
    2014-09-20 07:50:33 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallProperty(PackageInstallProperty pkg)
    2014-09-20 07:50:33 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.ExecuteAction(String actionId)
    2014-09-20 07:50:33 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    2014-09-20 07:50:33 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2014-09-20 07:50:43 Slp: Watson Bucket 1 
     Original Parameter Values 
    2014-09-20 07:50:43 Slp: Parameter 0 : SQL Server 2008 R2@RTM@ 
    2014-09-20 07:50:43 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion 
    2014-09-20 07:50:43 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion 
    2014-09-20 07:50:43 Slp: Parameter 3 : System.ArgumentNullException@-2147467261 
    2014-09-20 07:50:43 Slp: Parameter 4 : System.ArgumentNullException@-2147467261 
    2014-09-20 07:50:43 Slp: Parameter 5 : SetFeatureInstallStateAction 
    2014-09-20 07:50:43 Slp: 
     Final Parameter Values 
    2014-09-20 07:50:43 Slp: Parameter 0 : SQL Server 2008 R2@RTM@ 
    2014-09-20 07:50:43 Slp: Parameter 1 : 0x2AA348CC 
    2014-09-20 07:50:43 Slp: Parameter 2 : 0x2AA348CC 
    2014-09-20 07:50:43 Slp: Parameter 3 : 0xF15156D0 
    2014-09-20 07:50:43 Slp: Parameter 4 : 0xF15156D0 
    2014-09-20 07:50:43 Slp: Parameter 5 : SetFeatureInstallStateAction 
    2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_, Win32 error
    2
    2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_, Win32 error 2
    2014-09-20 07:50:44 Slp: Value cannot be null.
    Parameter name: productVersion
    2014-09-20 07:50:44 Slp: Watson bucket for exception based failure has been created
    2014-09-20 07:50:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey 
    2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
    2014-09-20 07:50:44 Slp: Sco: Attempting to get registry value DW0200
    2014-09-20 07:50:46 Slp: Submitted 1 of 1 failures to the Watson data repository
    2014-09-20 07:50:46 Slp: 
    2014-09-20 07:50:46 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:46 Slp: 
    2014-09-20 07:50:46 Slp: Error result: 1269611253
    2014-09-20 07:50:46 Slp: Result facility code: 940
    2014-09-20 07:50:46 Slp: Result error code: 47861

    2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_, Win32
    error 2
    2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_, Win32 error 2
    2014-09-20 07:50:44 Slp: Value cannot be null.
    Parameter name: productVersion
    2014-09-20 07:50:44 Slp: Watson bucket for exception based failure has been created
    2014-09-20 07:50:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey 
    2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
    2014-09-20 07:50:44 Slp: Sco: Attempting to get registry value DW0200
    2014-09-20 07:50:46 Slp: Submitted 1 of 1 failures to the Watson data repository
    2014-09-20 07:50:46 Slp: 
    2014-09-20 07:50:46 Slp: ----------------------------------------------------------------------
    2014-09-20 07:50:46 Slp: 
    2014-09-20 07:50:46 Slp: Error result: 1269611253
    2014-09-20 07:50:46 Slp: Result facility code: 940
    2014-09-20 07:50:46 Slp: Result error code: 47861
    Hi,
    For above error the error code is 2 which means system cannot find the file specified. It is saying it is unable to write at location which means SQL server account does not have access to
    C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    You can manually go to the location and add required rights may be installable is corrupt
    Now did you ran SQL server setup as administrator. Always right click on setup.exe file and select run as administrator.
    Please make sure you disable antivirus running on machine. Also if you have any registry scanner software which scans registry remove it as well.
    Below thread might be helpful
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/d425791a-9a7c-4c16-9e93-d348ecde3a3f/sql-server-2008-r2-install-fails-on-win-2008-r2-x64-std-server-with-workflowxmltext-msg-error-help?forum=sqlsetupandupgrade
    Can you also post summary.txt file
    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 server connection error

    Hi All,
    I am pulling data from SQL server(view) using WCF-SQL adapter, in DEV it's working fine and in test following is the error
    I have checked the credentials and server name all are fine, But i couldn't figure out the issue.
    Thanks in Advace
    Recloc_WCFSQL
    mssql://SQLSERVERTest/biztalkdb?InboundId=xyz
    WCF-SQL
    Microsoft.ServiceModel.Channels.Common.ConnectionException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that
    SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) ---> System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing
    a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance
    Specified) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock,
    Boolean asyncClose) at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
    at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover) at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo
    serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer
    timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString
    connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
    options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection
    owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
    at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout,
    Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions
    userOptions, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal&
    connection) at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection
    outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1
    retry) at System.Data.SqlClient.SqlConnection.Open() at Microsoft.Adapters.Sql.SqlAdapterConnection.OpenConnection() --- End of inner exception stack trace --- at Microsoft.Adapters.Sql.SqlAdapterConnection.OpenConnection() at Microsoft.Adapters.Sql.ASDKConnection.Open(TimeSpan
    timeout) at Microsoft.ServiceModel.Channels.Common.Design.ConnectionPool.GetConnection(Guid clientId, TimeSpan timeout) at Microsoft.ServiceModel.Channels.Common.Design.ConnectionPool.GetConnectionHandler[TConnectionHandler](Guid clientId, TimeSpan timeout,
    MetadataLookup metadataLookup, String& connectionId) at Microsoft.ServiceModel.Channels.Common.Channels.AdapterChannelListener`1.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan
    timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint.Enable()
    at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint..ctor(BizTalkEndpointContext endpointContext, IBTTransportProxy transportProxy, ControlledTermination control) at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiver`2.AddReceiveEndpoint(String url,
    IPropertyBag adapterConfig, IPropertyBag bizTalkConfig)

    The first few things to check would be
    Is TCP/IP Protocol enabled on the Test SQL Server Instance?
    If it is configured is it running on the default port or a different port has been specified? In case a different port has been specified then your configuration URI should reflect that OR the SQLBrowser service needs to be running
    The MS DTC configuration on the SQL Server need to have been configured with BOTH inbound/outbound enabled (Component Management - DTC)
    The Windows Firewall on the BizTalk Server Test should be a) disabled or b) configured to permit connection to the SQL Server on either 1433 or the specific instance port.
    Regards.

  • SQL Server 2000 to Oracle 9i

    Hi,
    I have a "Test" SQL Server DB with a "test" table. When I try to capture the source DB (SQL Server). It generated many errors:
    EXCEPTION: SQLServer2kSourceModelMap.mapPrimaryKeys():test.null.null;java.util.NoSuchElementException
    EXCEPTION: SQLServer2kSourceModelMap.mapTables():null.[null].[null];oracle.mtg.migration.MigraionSQLException:ORA:ORA-00903:invalid table name.
    I can see the table in the Source Model view, am I missing something?
    thanks
    louisa

    This looks like a Windows NT Logins problem. The workbench only works with object owbed by user that
    log on with SQL Server authentication. It can't match who owns what objects, uses null and then there
    are PK violations in the Workbenhc Repository.
    If you transfer the database from one machine to another you may also need to sun sp_changedbowner to get the ids in the database to match up with the new master db.
    Jim.

  • SQL Server 2012 BI Features (Standart Edition)

    Hello everyone
    I've a question about licensing in SharePoint and SQL Server. Firstly, we are using SharePoint 2013 Enterprise edition and SQL Server 2012 Standart edition. Which of  tools below are  possible use integrated with SharePoint 2013 with our current
    SQL Server Edition? 
    -PowerView
    -PowerPivot
    -SSRS 
    Also, is it possible to Analysis services intensively with our SQL server Standtart edition? For instance, creating cubes,data mining, forecasting, etc.. ?
    Thanks in advance..

    Hi Omnipotent06,
    Reporting Services in SharePoint mode is a collection of server components that provide report generation and delivery, based on Microsoft SQL Server and Microsoft SharePoint products. But different features are supported by the different
    editions of SQL Server 2012. If we are using SQL Server 2012 Standard edition, there are many limitations. For example, Power View and PowerPivot are not supported in SQL Server 2012 Standard edition.
    It supports most features of Reporting Services, except Data driven report subscription, Scale out deployment(Web farms) and Alerting. As to Analysis Services, it supports Backup/Restore, Attach/Detach databases, High Availability and
    Programmability (AMO, ADOMD.Net, OLEDB, XML/A, ASSL) features. For more details, please see the following document:
    http://technet.microsoft.com/en-us/library/cc645993.aspx
    The following excellent article is for your reference:
    Installing Reporting Services SharePoint Mode Report Server for Power View and Data Alerting
    Hope this helps.
    Thanks,
    Katherine Xiong
    If you have any feedback on our support, please click
    here.
    Katherine Xiong
    TechNet Community Support

  • Good device to put Instance root directory on a SQL Server 2012 Always On Failover Cluster ?

    Hello, I'm currently testing SQL Server 2012 AlwaysOn Failover Cluster.
    I wonder if I installed it correctly : I installed the software on both server with the instance root directory set to a directory on a cluster shared module.
    The reason why I'm not sure is because, when I wanted to upgrade from SP1 to SP2, I wanted to do it first on the passive node, but it failed for most of the components it had to upgrade. So I first upgraded the active node then failover and upgraded the
    newly active node.
    I installed SQL Server this way because our system admins don't like us to install in on C:\ for their own reasons (maybe backup, or something ...)
    I'm pretty sure there is something wrong. What's your point ?
    Thanks in advance.

    >I wonder if I installed it correctly : I installed the software on both server with the instance root directory set to a directory on a cluster shared module.
    Nope. 
    SQL Server 2012 and earlier don't support data files on CSV volumes (SQL 2014 does).
    And for any version of SQL Server the SQL Server instance directory should not be on a clustered disk.  The Installation is local to each node, so should be on a non-clustered disk.  It may be supported to put the instances in different locations
    on the same clustered disk, but I wouldn't recommend it. 
    Installing the SQL Binaries on C:\ is fine.  If you have another local volume you can also install them there.
    David
    David http://blogs.msdn.com/b/dbrowne/

  • Error upgrading to 2012 R2 - SQL Server Certificate problems

    We are experiencing some strange errors during the installation of Config Mgr 2012 R2. The installer does not provide any errors, it just exits during the final steps. The c:\configmgrsetup.log file shows:
    INFO: Testing SQL Server [SQL01.ad.edu] connection ...  $$<Configuration Manager Setup><11-21-2013 13:47:25.427+360><thread=1984 (0x7C0)>
    INFO: SQL Connection succeeded. Connection: SQL01.AD.EDU MASTER, Type: Unsecure  $$<Configuration Manager Setup><11-21-2013 13:47:25.433+360><thread=1984 (0x7C0)>
    INFO: Tested SQL Server [SQL01.ad.edu] connection successfully.  Any preceding SQL connection errors may be safely ignored.  $$<Configuration Manager Setup><11-21-2013 13:47:25.438+360><thread=1984 (0x7C0)>
    INFO: Certificate: 3082022B38D<!Removed characters for readability!>C1D9C921A058D19F  $$<Configuration Manager Setup><11-21-2013 13:47:25.443+360><thread=1984 (0x7C0)>
      ERROR: Failed to open certificate store (HRESULT=0x5)  $$<Configuration Manager Setup><11-21-2013 13:47:25.451+360><thread=1984 (0x7C0)>
    Failed to write sql server certificate to store (TrustedPeople) on site server (SCCM.ad.edu).  $$<Configuration Manager Setup><11-21-2013 13:47:25.457+360><thread=1984 (0x7C0)>
    ERROR: Failed to configure SQL Server Certificate.  $$<Configuration Manager Setup><11-21-2013 13:47:25.462+360><thread=1984 (0x7C0)>
    Failed to create SQL Server Certificate, ConfigMgr installation cannot be completed.  $$<Configuration Manager Setup><11-21-2013 13:47:25.468+360><thread=1984 (0x7C0)>
    <11-21-2013 13:47:25> Failed to create process of SetupWpf.exe.
    We are running SQL on our enterprise 2008R2 SQL server and SCCM runs on a dedicated 2012 Server. Certificates are generally signed by our CA but the SQL certificate for ConfigMgr is self signed and appears to be trusted by the SCCM server (it appears in
    the TrustedPeople store). We have been running properly using HTTPS and the only errors prior to attempting the upgrade were with a secondary distribution point that had been removed prior to install. A new SQL certificate has been generated and tested but
    yields the same error messages. All suggestions are appreciated. Thanks,
    -Brandon

    Hi,
    I found a similar article for your reference.
    Fail to create SQL Server Certificate" during installation
    http://henkhoogendoorn.blogspot.nl/2013/01/fail-to-create-sql-server-certificate.html
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    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.

  • SQL SERVER Upgrade using different Language Media

    Hi
    I have a doubt.
    OS is Windows 2003 Server ( Japanese Version )
    SAP - ERP6.0 SR3 ( EN + JA Installed)
    My customer is having SQL Server 2000. ( Japanese Version ). While upgrading the SQL Server to 2005, can we use a English Version Media to upgrade the same.
    Thanking you in anticipation.
    Best Regards
    L Raghunahth.

    Lydia,
    I agree with regards to the 2012 version.  However, in SQL Server 2014, upgrading a database with a compatibility level of 90 sets
    the database to compatibility level 100. See link below...
    https://technet.microsoft.com/en-us/library/bb510680.aspx
    Shouldn't the 2014 version of the advisor tool issue the same warning seen in the screenshot of the msdn blog post we both mentioned?  As in... "After upgrade, compatibility levels <list of levels>, will be set to 100".
    Hi JJordheim,
    According to my test, SQL Server 2014 Upgrade Advisor also only raise warning when database compatibility level is less than 90 in the “SQL Server Parameters” page.
    From your description, when database compatibility level is set to 90, SQL Server 2014 Upgrade Advisor should also raise warning, right? If so , this is a design issue of SQL Server 2014 Upgrade Advisor, personally, I recommend you
    submit a feedback to the Microsoft Connect at this link
    https://connect.microsoft.com/SQLServer/Feedback . Your feedback enables Microsoft to offer the best software and deliver superior services.
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • Conversion Error During the Execution of SQL Server Job

    Hello,
    I have a production SQL server and a test SQL server that mimics the production server. On the production server all the jobs which do a variety of things using Transact SQL and SSIS packages work flawlessly. However one of the jobs on the test server fails
    at a step and issues the following error:
    executed as user: DomainName\administrator. Conversion failed when converting datetime from character string. [SQLSTATE 22007] (Error 241). 
    The step failed.
    Here is the code contained in the steps Command window (same exact code that works fine on the production server):
    declare @Now datetime
    declare @DB_Date datetime
    declare @Trip_Err datetime
    select @Now = convert(varchar,getdate(),101)
    select @DB_Date = (select convert(varchar,max(ProcessDate),101) from I_Loans)
    if @now <> @DB_Date
    begin
    truncate table I_Loans
    end
    else
    select @Trip_err = 'error'
    I don’t see anything preventing this code from executing. However, I am not a programmer. My SQL Server version is below:
    Microsoft SQL Server 2005 - 9.00.5324.00 (Intel X86)  
    Aug 24 2012 14:24:46   Copyright (c) 1988-2005 Microsoft Corporation 
    Standard Edition on Windows NT 6.0 (Build 6002: Service Pack 2)
    Any advice or solutions will be greatly appreciated. Please let me know if I need to provide more information.
    Thank you,
    Dave
    David Young

    Could you run this query from management studio in test?
    select convert(varchar,max(ProcessDate),101) from I_Loans
    It could be something to do with the ProcessDate value which had issues to convert
    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

  • Help! Licence for SQL Server 2008 VM on Windows 2012

    I am confused by latest Microsoft Virtual server licence for SQL Server 2008. 
    We have a Hyper-V host running Windows Server 2012 R2 Datacenter. Displayed in its Task Manager, it has 16 cores and 32 logical processors (with hyper-threading turned on). A SQL Server VM is running on this host with 10 Virtual processors (showing from Hper-V
    Manager). The SQL Server edition is SQL Server 2008 Standard. 
    We are using "Per Core Licensing Model". Now, the question is how many licences we need to purchase for the above SQL Server?
    There are "SQL Server 2008 Licensing Guide", "Microsoft SQL Server 2012 Virtualization Licensing Guide" and "Microsoft SQL Server 2014 Licensing Guide". But none of them covers this scenario, which is running SQL Server 2008 on
    Windows 2012 Hyper-V host Server.
    Could you please provide me your opinion: Should I license 10 cores for the SQL Server VM or license 5 cores (because the hyper-threading on physical server) ? Thank you very much in advance! 

    I am confused by latest Microsoft Virtual server licence for SQL Server 2008. 
    We have a Hyper-V host running Windows Server 2012 R2 Datacenter. Displayed in its Task Manager, it has 16 cores and 32 logical processors (with hyper-threading turned on). A SQL Server VM is running on this host with 10 Virtual processors (showing from Hper-V
    Manager). The SQL Server edition is SQL Server 2008 Standard. 
    We are using "Per Core Licensing Model". Now, the question is how many licences we need to purchase for the above SQL Server?
    There are "SQL Server 2008 Licensing Guide", "Microsoft SQL Server 2012 Virtualization Licensing Guide" and "Microsoft SQL Server 2014 Licensing Guide". But none of them covers this scenario, which is running SQL Server 2008 on
    Windows 2012 Hyper-V host Server.
    Could you please provide me your opinion: Should I license 10 cores for the SQL Server VM or license 5 cores (because the hyper-threading on physical server) ? Thank you very much in advance!

Maybe you are looking for