hello,

for testing and developing i have installed Microsoft SQL Server 2017 Developer (German) to my computer.

yesterday i decided to upgrade to Microsoft SQL Server 2019 Developer (German). the upgrade to 2019 was successfully, but i thought after an upgrade all old SQL Server 2017 would be removed, but it wasn't. i still have all the SQL Server 2017 menu entries on start menu and all the old Microsoft SQL Server 2017 Setup entry in the uninstall control panel.

i now tried to uninstall the SQL server 2017 setup but then i get always the warning 26003:

ok, then i tried to uninstall SQL Server 2019 as well and that will show up a very similar warning dialog:

i want to uninstall all SQL Server (2017 & 2019) from my computer to reinstall only SQL Server 2019 - because i don't have so much diskspace left.

at the moment i am not able to uninstall SQL Server 2019 nor SQL Server 2017.

there are older posts for "solutions" of warning 26003 available, to browse the regitries and remove everything that looks like part of SQL Server, but only for very old SQL Server 2008.
i mean in the meantime there should be a more safe reliable automatic solution available without hacking around...

Hi, 

Since I installed ssms 18.x, I have trouble when I want to create a new extended session, following theses steps "management->Extended Event->Sessions" click right on "new session." When the dialog box is open, I click on "events."  and the list of events remains desperately empty.
I make a screenshot see below.
I already tried to uninstall and install again(with a reboot).
I tried to re-install the french edition with the same issues.

zoltix

Hello everyone, when I try to install SQL Server 2017 at the end of installation it appears to me "Unable to install SQL Server (setup.exe)" .

Here attached the log folder: https://1drv.ms/u/s!AqlJGBcqay33jkpNKOfZtKF7hU8-?e=88DefF

Try to execute FixDotNet and I got the following output: https://1drv.ms/u/s!AqlJGBcqay33jkk7lMh9ybMiC79p?e=uH7pUB

team ,

we have  ServerA  which is SQL 2016 Std edition, we plan to upgrade it to SQL 2016 Enterprises.

edition upgrade  (in-place upgrade)

https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades?view=sql-server-ver15

this serverA is subscriber server  of Transaction Replication.   ( publisher & distributer & agent running on SQL 2016Ent on different server)

• so when i perform edition upgrade of SQL 2016 Std to entpr for ServerA.
• what are the things to take care ?
• stop distribution agent  on Publisher ? or need to stop log reader agent also?

hi,

we have plan to upgrade SQL 2019 from sql 2016 production sql server. (live server with heavy applications transactions)

do we need to stop database calls during  sql 2016 upgrade?

Is restart of server is mandatory or optional?

What is the best way to set up a sql server on vmware for best performance?  We have plenty of memory however we’re not sure the best way to configure the vCPUs.  Right now our primary sql server has 1 socket with 4 virtual processors.  I read somewhere that best practice for sql was to have 1 processor per socket?

I've been trying to install SQL server 2019, only database engine but it keeps failing. This is the error log:

We had a Windows Server 2019 server running SQL Server 2017 connected to the domain controller of an Windows Small Business Server 2011.  The SBS Server was replaced by a new Windows Server 2019 domain controller using the same name and IP address.  We rebuilt the trust relationship of the Windows server running SQL server to the new Windows domain controller with the following command in PowerShell.

Reset-ComputerMachinePassword -Server SERVERNAME -Credential DOMAIN\Administrator

That part worked fine, but now the SQL Server services "SQL Server (MSSQLSERVER) and "SQL Server Agent (MSSQLSERVER)" services won't start.  In fact, they can't even be manually started since they are greyed out.

Reversing the process, and going back to the SBS 2011 domain controller resulted in the services working again.

I am not sure why these services won't start with the new domain controller.  Any help would be appreciated.

Michael

Hello,

on a new project I have been assigned a role of a database administrator. My background is mobile application development, so this is a whole new existing world to me.

I am supposed to add a third SQL Server node to an existing failover cluster. Unfortunately, in the "Add Node" installation wizard there are no clusters to be selected from the dropdown menu.

Things I have already tried:

• check wheter all nodes can access the admin shares of each other (they do)
• install the third node as standalone server and the adding it do the cluster
• add the third node to the cluster without prior installation
• ping all nodes, Windows server failover cluster, and SQL failover cluster (everything is ping'able)
• turn off firewalls on all of the nodes
• update the windows server (all nodes are up-to-date)

Configuration of the cluster:

• Always On cluster without a shared storage
• Each node has four drives (C:\, SQL data, SQL temp & backup, SQL Logs)
• All three nodes are members of the same domain
• All three nodes are memebers of the same Windows failover cluster (there was no issue with adding the third node)

I couldn't find any other workaround or solution to my probem, that is why I am asking you (experienced database admins) for help!

Hello everyone,

I have a question, is it possible to activate my trial version of Sql server 2016 Entreprise with a product key for Sql server 2017 Entreprise ?

if no what are my options ?

thank you very much in advance.

Hi Pros,

Does anyone know how to fix this error below? I'm running Python in-database using SQL Server 2017. The coding environment should have been set up properly and run code without any problems up until last week and I didn't make any changes on the SQL Server or anything.

===========================================

sample code

exec sp_execute_external_script @language=N'Python',@script=N'OutputDataSet = InputDataSet
print("Input data is {0}".format(InputDataSet))
',@input_data_1= N'SELECT 1 as col'

===========================================

error message

Msg 39012, Level 16, State 1, Line 25 Unable to communicate with the runtime for 'Python' script. Please check the requirements of 'Python' runtime. STDERR message(s) from external script: Traceback (most recent call last): File "", line 1, in File"C:\Program Files\Microsoft SQL Server\MSSQL14.SQL2017\PYTHON_SERVICES\lib\site-packages\revoscalepy__init__.py", line 6, in from .RxSerializable import RxMissingValues File "C:\Program Files\Microsoft SQL Server\MSSQL14.SQL2017\PYTHON_SERVICES\lib\site-packages\revoscalepy\RxSerializable.py", line 11, in from pandas import DataFrame File "C:\Program Files\Microsoft SQL Server\MSSQL14.SQL2017\PYTHON_SERVICES\lib\site-packages\pandas__init__.py", line 39, in from pandas.core.api import * File "C:\Program Files\Microsoft SQL Server\MSSQL14.SQL2017\PYTHON_SERVICES\lib\site-packages\pandas\core\api.py", line 10, in from pandas.core.groupby import Grouper File "C:\Program Files\Microsoft SQL Server\MSSQL14.SQL2017\PYTHON_SERVICES\lib\site-packages\pandas\core\groupby__init__.py", line 2, in

STDERR message(s) from external script: from pandas.core.groupby.groupby import ( File "C:\Program Files\Microsoft SQL Server\MSSQL14.SQL2017\PYTHON_SERVICES\lib\site-packages\pandas\core\groupby\groupby.py", line 20, in from pandas.core.dtypes.common import ( File "C:\Program Files\Microsoft SQL Server\MSSQL14.SQL2017\PYTHON_SERVICES\lib\site-packages\pandas\core\dtypes\common.py", line 17, in from .inference import is_string_like, is_list_like File "C:\Program Files\Microsoft SQL Server\MSSQL14.SQL2017\PYTHON_SERVICES\lib\site-packages\pandas\core\dtypes\inference.py", line 8, in from pandas.compat import (PY2, string_types, text_type, ImportError: cannot import name 're_type'

Hi All,

I've been trying to automate the installation of SQL Server using the experiment DSC Module for SQL Server.  This issue occurs in my vagrant environments and vCenter environments.

This is the entirety of the script that does the meat and potatoes of the install.

#use xSQLServerSetup of xSQLServer
#sql install error log can be found at C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\log
param (
    [string]$SetupCredA = $(throw "error -SetupCredA is required.  Need installer username."),
    [string]$SetupCredPW = $(throw "error -SetupCredPW is required.  Need installer password."),
	[string]$SvcAccountCredA = $(throw "error -SvcAccountCred is required.  Need to know service account."),
    [string]$SvcAccountPW = $(throw "error -SvcAccountCred is required.  Need to know service account pw."),
    [string]$Features = $(throw "error -Features is required."),	
    [string]$SAArray = $(throw "error -SAArray is required.  Need to know sysadmins.")
 )
$SetupCred=New-Object System.Management.Automation.PSCredential ($SetupCredA, $(ConvertTo-SecureString $SetupCredPW -AsPlainText -Force))
$SvcAccountCred=New-Object System.Management.Automation.PSCredential ($SvcAccountCredA, $(ConvertTo-SecureString $SvcAccountPW -AsPlainText -Force))
$Extract="C:\InstallSQL"
$ServerCoreFeatures="SQLENGINE,REPLICATION,FULLTEXT,AS,CONN,IS,SNAC_SDK"
$ServerGUIFeatures="SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,MDS,DREPLAY_CTLR,DREPLAY_CLT"
$ServerGUIFeaturesWithReporting="$ServerGUIFeatures,RS"
$ReportServerFeatures="RS"

switch ($Features) {
    "ServerCoreFeatures" { $Features = $ServerCoreFeatures }"ServerGUIFeatures" { $Features = $ServerGUIFeatures }"ServerGUIFeaturesWithReporting" { $Features = $ServerGUIFeaturesWithReporting }"ReportServerFeatures" { $Features = $ReportServerFeatures }
}

$configData = @{
    AllNodes = @(
          @{
                NodeName = "$($env:computername)"
                PSDscAllowPlainTextPassword = $true
           }
         )
}

Configuration SetupSQL
{
    Import-DSCResource -ModuleName xSQLServer
    Node "$($env:computername)"
    {
        xSQLServerSetup Install-SQL
        {
            SourcePath = $Extract
            SourceFolder = "SQL2014"
            SetupCredential = $SetupCred
            #-------------
            SQLSvcAccount = $SvcAccountCred
            AgtSvcAccount = $SvcAccountCred
            SQLSysAdminAccounts = $SAArray
            #--------------------
            UpdateEnabled = "False"
            UpdateSource = "$Extract\SQL2014\Updates"
            #-----------------
            ErrorReporting = "True"
            #-----------------
            SQLUserDBDir = "M:\Data"
            SQLUserDBLogDir = "L:\Log"
            SQLTempDBDir = "T:\TempDB"
            SQLTempDBLogDir = "T:\TempLog"
            SQLBackupDir = "M:\Backup"
            #-----------------
            InstanceName= "MSSQLSERVER"
            Features = $Features
        }
    }

}
SetupSQL -ConfigurationData $configData
Start-DscConfiguration .\SetupSQL -force -wait -verbose

The environment is prestaged with

$Modules="C:\Program Files\WindowsPowerShell\Modules"
$Extract="C:\InstallSQL"
$ResourceKit="$Extract\DSCRK9.zip"
$WinSXSFiles="$Extract\sxsfiles.zip"
$SQLInstall="$Extract\SQL2014.zip"
mkdir $Extract -force
write-host "$(get-date) Downloading install resources"
start-bitstransfer "http://downloads.yosemite.local/files/application/microsoft/sqlinstall/dscrk9.zip" $ResourceKit
start-bitstransfer "http://downloads.yosemite.local/files/application/microsoft/sqlinstall/sxsfiles.zip" $WinSXSFiles
start-bitstransfer "http://downloads.yosemite.local/files/application/microsoft/sqlinstall/sql2014.zip" $SQLInstall
write-host "$(get-date) Download completed"
Configuration PreStageSQL
{
    Archive Extract-Resource-Kits
    {
        Ensure = "Present"
        Path = $ResourceKit
        Destination = $Extract        
    }

    Archive Extract-WinSXS-Files
    {
        Ensure = "Present"
        Path = $WinSXSFiles
        Destination = $Extract
        DependsOn = "[Archive]Extract-Resource-Kits"
    }
	Archive Extract-SQL-Files
    {
        Ensure = "Present"
        Path = $SQLInstall
        Destination = $Extract
        DependsOn = "[Archive]Extract-WinSXS-Files"
    }
	File Move-Resource-Files
    {
       SourcePath = "$Extract\All Resources"
       DestinationPath = $Modules
       Ensure = "Present"
       Type = "Directory"
       Recurse = $True
       MatchSource = $True
       DependsOn = "[Archive]Extract-SQL-Files"
    }
	WindowsFeature Install-NET35
    {
        Name = "NET-Framework-Core"
        Source = "$Extract\sxs"
        Ensure = "Present"
        DependsOn = "[File]Move-Resource-Files"
    }

}
PreStageSQL
Start-DscConfiguration .\PreStageSQL -force -wait -verbose
write-host "$(get-date) completed"

The setup errors out at the end with the following messages in the console/event log.  The SQL Install itself appears to be complete.  I've tried this with UpdateEnabled = "true" as well and it errors at the same location.

So the install appears to complete successfully but powershell reports an error

'C:\InstallSQL\SQL2014\setup.exe' started in process ID 192
VERBOSE: [WINDOWS2012R2]:                            [[xSQLServerSetup]Install-SQL] Importing function 'NetUse'.
VERBOSE: [WINDOWS2012R2]:                            [[xSQLServerSetup]Install-SQL] Importing function 'ResolvePath'.
VERBOSE: [WINDOWS2012R2]:                            [[xSQLServerSetup]Install-SQL] Importing function
'StartWin32Process'.
VERBOSE: [WINDOWS2012R2]:                            [[xSQLServerSetup]Install-SQL] Importing function
'WaitForWin32ProcessEnd'.
VERBOSE: [WINDOWS2012R2]:                            [[xSQLServerSetup]Install-SQL] Path:
C:\InstallSQL\SQL2014\setup.exe
VERBOSE: [WINDOWS2012R2]: LCM:  [ End    Set      ]  [[xSQLServerSetup]Install-SQL]  in 500.8120 seconds.
PowerShell DSC resource MSFT_xSQLServerSetup  failed to execute Set-TargetResource functionality with error message:
Set-TargetResouce failed+ CategoryInfo          : InvalidOperation: (:) [], CimException+ FullyQualifiedErrorId : ProviderOperationExecutionFailure+ PSComputerName        : WINDOWS2012R2

The SendConfigurationApply function did not succeed.
    + CategoryInfo          : NotSpecified: (root/Microsoft/...gurationManager:String) [], CimException+ FullyQualifiedErrorId : MI RESULT 1+ PSComputerName        : WINDOWS2012R2

VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 501.455 seconds

With the following errors in event viewer.  

Job {5E0C5C09-B7B2-11E4-80B6-000C29F93310} : 
Message Set-TargetResouce failed 
HResult -2146233087 
StackTrack    at System.Management.Automation.Interpreter.ThrowInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

Job {5E0C5C09-B7B2-11E4-80B6-000C29F93310} : 
This event indicates that failure happens when LCM is processing the configuration. ErrorId is 0x1. ErrorDetail is The SendConfigurationApply function did not succeed.. ResourceId is [xSQLServerSetup]Install-SQL and SourceInfo is C:\InstallSQL\InstallSQL.ps1::41::9::xSQLServerSetup. ErrorMessage is PowerShell DSC resource MSFT_xSQLServerSetup  failed to execute Set-TargetResource functionality with error message: Set-TargetResouce failed .

Job {5E0C5C09-B7B2-11E4-80B6-000C29F93310} : 
DSC Engine Error : 
	 Error Message The SendConfigurationApply function did not succeed. 
	Error Code : 1 

Overall summary:
  Final result:                  Passed
  Exit code (Decimal):           0
  Start time:                    2015-02-18 21:09:08
  End time:                      2015-02-18 21:17:01
  Requested action:              Install

Machine Properties:
  Machine name:                  WINDOWS2012R2
  Machine processor count:       2
  OS version:                    Windows Server 2012
  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

Package properties:
  Description:                   Microsoft SQL Server 2014 
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       0
  Installation location:         C:\InstallSQL\SQL2014\x64\setup\
  Installation edition:          Enterprise Edition: Core-based Licensing

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 Administrator
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Automatic
  ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
  ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
  ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            Administrator
  ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   
  CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
  CLTSTARTUPTYPE:                Manual
  CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150218_210907\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               Manual
  CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     
  ENABLERANU:                    false
  ENU:                           true
  ERRORREPORTING:                true
  FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
  FTSVCPASSWORD:                 <empty>
  HELP:                          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 Service\MsDtsServer120
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         true
  QUIETSIMPLE:                   false
  ROLE:                          
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  C:\Backup
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 Administrator
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           Administrator, Administrator
  SQLTEMPDBDIR:                  C:\TempDB
  SQLTEMPDBLOGDIR:               C:\TempLog
  SQLUSERDBDIR:                  C:\Data
  SQLUSERDBLOGDIR:               C:\Log
  SQMREPORTING:                  false
  TCPENABLED:                    1
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  C:\InstallSQL\SQL2014\Updates
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150218_210907\ConfigurationFile.ini

Detailed results:
  Feature:                       Management Tools - Complete
  Status:                        Passed

  Feature:                       Client Tools Connectivity
  Status:                        Passed

  Feature:                       Client Tools SDK
  Status:                        Passed

  Feature:                       Client Tools Backwards Compatibility
  Status:                        Passed

  Feature:                       Management Tools - Basic
  Status:                        Passed

  Feature:                       Database Engine Services
  Status:                        Passed

  Feature:                       Data Quality Services
  Status:                        Passed

  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Passed

  Feature:                       SQL Server Replication
  Status:                        Passed

  Feature:                       Master Data Services
  Status:                        Passed

  Feature:                       Distributed Replay Client
  Status:                        Passed

  Feature:                       Distributed Replay Controller
  Status:                        Passed

  Feature:                       Integration Services
  Status:                        Passed

  Feature:                       Data Quality Client
  Status:                        Passed

  Feature:                       Analysis Services
  Status:                        Passed

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       Documentation Components
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       SQL Client Connectivity
  Status:                        Passed

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed

  Feature:                       Setup Support Files
  Status:                        Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150218_210907\SystemConfigurationCheck_Report.htm

The mandatory update from Microsoft this past week seems to have trashed my ability to import Excel files into SQL Server.  It says Excel isn't a valid connection manager type.  I've reinstalled Office and the ACE Database Runtimes, with no success.

My next idea is to reinstall or repair SQL Server 2017, the developer edition.  I started to try repair, but that requires the install media files.  On the download website, there are two options: an ISO or CAB files.  I'm not sure which the repair needs.  If you can tell me, that might help.

Further if you have any other suggestions on remedying this error, that would be great:

In SSMS, I clicked on on of the databases and selected Task, then import data, select Excel, and I see this error immediately.

I'm running SQL Server 2017 Developer Edition and the most current version of SSDT (just downloaded and installed as an attempt to fix this issue).  The machine is 64-bit Windows 2012 R2.

I'm running Microsoft Office 365 64-bit, but again, things have been running perfectly until today with SSIS accessing Excel.

My guess is that something, perhaps in yesterday's Windows update corrupted, whatever it is that SQL needs to connect to an Excel data source, but that's only a guess.

I have installed the 64-bit versions of 

Microsoft.ACE.OLEDB.12.0

Microsoft.ACE.OLEDB.15.0

Microsoft.ACE.OLEDB.16.0

Any possible solution?  Is there something I need to reinstall?  Please advise.

Hi fellas, had a Licensing question regarding SQL.

If I have a single physical host with, say, 12 physical cores, and I go with a core-based licensing model, does that permit me to install as many VMs running SQL Enterprise as I can on that host?

Hi,

I am getting the following error when trying to install SQL Server 2008 R2 Management Studio (SQLManagementStudio_x86_ENU.exe or SQLManagementStudio_x64_ENU.exe) on a new Toshiba Portege R830-10R:

Another version of Microsoft Visual Studio 2008 has been detected on this system that must be updated to SP1.  Please update all Visual Studio 2008 installations to SP1 level, by visiting Microsoft Update.

I have all Windows Updates installed on this machine and I DO NOT have VS 2008 installed on this computer (VS2008 was never installed on this computer), but VS 2010 SP1 with .Net Framework 4.0 SP1!

I have sent all day trying to install either ones of the above .exe, but always get the same error message.

I have checked the registry and see that I do not have a  HKLM\SOFTWARE\Microsoft\DevDiv\VS key but only a HKLM\SOFTWARE\Microsoft\DevDiv\VC key (probably since I configured VS1010 for C#).  The HKLM\SOFTWARE\Microsoft\DevDiv\VC\Servicing\9.0 contains SP = 1 and SPIndex = 1.

Please help.
Thanks.

Eric

I have a production SQL Server 2017 that I need to rejoin to a different domain controller.  Has anyone here done that, and what happened?  What settings had to be changed to get SQL Server back running?

Since it is a production server, I don't want to get myself into a bind where I can't go forwards or backwards.

Thanks!