On 26 of July I was enforced by Windows 10 to update my OS (to version 1903) and few other updates were queued to be installed, also SQL Server 2016 Service Pack 1 GDR update (KB4505219).

It was major Windows update which took a long time so I left it for the night to be updated.

In the morning I had a very unpleasant surprise. Windows was updated indeed to new version, SQL server update failed, and my data was gone. I keep all applications on C:\ partition, but some updates wiped my D:\ partition where was no files related to any MS service, I had only one database files in there which could be somehow correlated.

My suspicion that SQL Server update may be responsible for that data wipe comes from scanning D:\ partition with couple of simple programs to files restore. They all show that last files which appear on that partition are SQL Server files which have should never been there. The full list in the file

https://1drv.ms/t/s!Alry_rVH97JyngkEnk241F92STmy?e=vdS6Qx

I talked to first line MS support and of course they stated that this is impossible to happen during Windows update. But there are many comments on the Internet with similar problems of losing data after Windows update to version 1903. But no track with problems related to SQL Server updates. I will leave it here as a warning.

Unfortunately, I received a lesson straight from MS to start doing full backups. Restoring lost files from wiped partition would cost me hundreds of dollars, so I just have to deal with losing them.

It just would be nice if all updates enforced by OS and other MS applications would be safe and tested more carefully before release.

After a trial of SQL 2017, we purchased the product with product key.

HI All,

I am currently running a SQL server 2014 standard edition, which holds 6 TB of databases.

planning to upgrade on SQL server 2017 but not sure if i should go for Enterprise edition or standard itself, it has huge cost differences.

I just needed your suggestion or points so that i can convince myself for moving it onto enterprise edition and what restrictions will always be there with standard edition.

Databases growing 1 TB in a year.

SQL Server DBA

Hi All,

if SQL 2016 standard with Server 2016 standard should be all fine.

How about SQL 2014 standard + Server 2016. standard?

Thanks.

While trying to install SQL server Express 2017 the setup exists with the following error. It says couldnt find the the registry key also the MOF compiler could connect with the WMI server. I am not sure whats happening after I uninstalled 2014 to have 2017.

Thanks!!

Overall summary:

  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068119551
  Exit facility code:            1211
  Exit error code:               1
  Exit message:                  Cannot find registry key 'SOFTWARE\Microsoft\Microsoft SQL Server\140\ConfigurationState'.
  Start time:                    2019-08-05 16:14:59
  End time:                      2019-08-05 16:15:32
  Requested action:              Install
  Exception help link:           https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0xF96176E5%400xD3BEBD98%401211%401&EvtType=0xF96176E5%400xD3BEBD98%401211%401

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
  Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.


Machine Properties:
  Machine name:                  DESKTOP-EQCMC00
  Machine processor count:       4
  OS version:                    Microsoft Windows 10 Home (10.0.17134)
  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 2017 
  ProductName:                   SQL Server 2017
  Type:                          RTM
  Version:                       14
  SPLevel:                       0
  Installation location:         C:\SQLServer2017Media\Express_ENU\x64\setup\
  Installation edition:          Express

Product Update Status:
  User selected not to include product updates.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      true
  AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Disabled
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  TABULAR
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTELSVCACCT:                  <empty>
  ASTELSVCPASSWORD:              <empty>
  ASTELSVCSTARTUPTYPE:           0
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190805_161456\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTPYTHONLICENSETERMS:     false
  IACCEPTROPENLICENSETERMS:      false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              true
  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:                    SQLEXPRESS
  INSTANCENAME:                  SQLEXPRESS
  ISMASTERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISMASTERSVCPASSWORD:           <empty>
  ISMASTERSVCPORT:               8391
  ISMASTERSVCSSLCERTCN:          <empty>
  ISMASTERSVCSTARTUPTYPE:        Automatic
  ISMASTERSVCTHUMBPRINT:         <empty>
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  ISTELSVCACCT:                  <empty>
  ISTELSVCPASSWORD:              <empty>
  ISTELSVCSTARTUPTYPE:           0
  ISWORKERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISWORKERSVCCERT:               <empty>
  ISWORKERSVCMASTER:             <empty>
  ISWORKERSVCPASSWORD:           <empty>
  ISWORKERSVCSTARTUPTYPE:        Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  MRCACHEDIRECTORY:              
  NPENABLED:                     0
  PBDMSSVCACCOUNT:               <empty>
  PBDMSSVCPASSWORD:              <empty>
  PBDMSSVCSTARTUPTYPE:           0
  PBENGSVCACCOUNT:               <empty>
  PBENGSVCPASSWORD:              <empty>
  PBENGSVCSTARTUPTYPE:           0
  PBPORTRANGE:                   <empty>
  PBSCALEOUT:                    false
  PID:                           *****
  QUIET:                         true
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
  SQLSVCINSTANTFILEINIT:         true
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           DESKTOP-EQCMC00\UjjalPC
  SQLTELSVCACCT:                 NT Service\SQLTELEMETRY$SQLEXPRESS
  SQLTELSVCPASSWORD:             <empty>
  SQLTELSVCSTARTUPTYPE:          Automatic
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBFILECOUNT:            1
  SQLTEMPDBFILEGROWTH:           64
  SQLTEMPDBFILESIZE:             8
  SQLTEMPDBLOGDIR:               <empty>
  SQLTEMPDBLOGFILEGROWTH:        64
  SQLTEMPDBLOGFILESIZE:          8
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 false
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190805_161456\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190805_161456\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639

  Feature:                       SQL Client Connectivity
  Status:                        Passed

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Failed
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190805_161456\SystemConfigurationCheck_Report.htm

Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented

Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    Message: 
        Cannot find registry key 'SOFTWARE\Microsoft\Microsoft SQL Server\140\ConfigurationState'.
    HResult : 0x84bb0001
        FacilityCode : 1211 (4bb)
        ErrorCode : 1 (0001)
    Data: 
      DisableWatson = true
    Stack: 
        at Microsoft.SqlServer.Configuration.Sco.FeatureRegistration.SetFeatureFlag(String machine, String featureId, String flagName, String registryKey, Object flagState, RegistryView cpuView)
        at Microsoft.SqlServer.Configuration.Sco.FeatureRegistration.SetFeatureConfigState(String featureId, ConfigurationState configState, String version, RegistryView cpuView)
        at Microsoft.SqlServer.Configuration.SetupExtension.UpgradeIncompleteFeatureConfigEventHandler.MarkFeatureConfigured(FeatureId featureId, ConfigActionScenario scenario, Dictionary`2 actionData, String instanceId, Boolean keepFailedState)
        at Microsoft.SqlServer.Configuration.SetupExtension.UpgradeIncompleteFeatureConfigEventHandler.FeatureConfigurationExecutionEventHandler(Object sender, FeatureConfigScenarioEventArgs eventArgs, Boolean runValidation, Boolean featureFailed)
        at Microsoft.SqlServer.Configuration.SetupExtension.UpgradeIncompleteFeatureConfigEventHandler.FeatureConfigurationExecutionEventHandler(Object sender, Object[] objectArray)
        at Microsoft.SqlServer.Chainer.Infrastructure.NotificationHandler.Invoke(Object notification, Object[] objectArray)
        at Microsoft.SqlServer.Chainer.Infrastructure.NotificationService.OnNotify(Object eventKey, Object notification, Object[] objectArray)
        at Microsoft.SqlServer.Configuration.ConfigExtension.ConfigFeatureActionListener.InFeatureConfigurationExecutionEventHandler(ActionKey key, TextWriter loggingStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifyInExecution(ActionKey actionRunning, TextWriter loggingStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)

Hello There,

 Kindly advise me pointer and useful inputs, views to consider on the SQL Server 2012 consolidation and Rationalization.

 In our environment there are 40 SQL Server Instances running. Business like to consolidate them as much as possible.

1 Where to start

2. what are the criteria,

3. how to assess the current performance

4. how to validate to ensure in terms performance and security post consolidation

Thanks, Siva SQL

Sivaprasad S http://sivasql.blogspot.comPlease click the Mark as Answer button if a post solves your problem!

Hi. I am DBA of SQL server 2014 Enterprise which is running on Windows Server 2012 R2.

I have added new server certificate to the DB server. After I confirmed the new server certificate are added correctly with correct FQDN name and expiration date from the MMC console of Certificate (Local Computer) > Personal > Certificate, then I right click the new cert > All Tasks > Manage Private Keys, and click "Add", and select "Service Accounts" from "Object Types", and enter service account name of SQL server service, and set only Read permission to it, and save the setting, and delete old server cert, then I reboot my DB server. However SQL Server service and SQL Server Agent service can not be started. I got following errors when I try to start it up manually.

I found the following error on Application event log.

----------------------------------------------

Event ID: 26014

Unable to load user-specified certificate [Cert Hash(sha1) "XXXXXXX"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online.

------------------------------------------------

I believed that is it to add service account of SQL server service from manage private key to the new server cert. Is there any other process required on this matter? Any advice will be gratefully appreciated. Thank you..

Hi,

I am going to remove an app server that has DB on dedicated (shared with others DBs) SQL server.

So my plan is :

1. Remove app server.

2. In visual studio of SQL server right click\delete the DB of removed app server.

Do I need to perform any other actions?

Thx.

--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Hi,

I am developing a desktop application and I want to protect my database from being examined (structure).

How can I do that?

Regards.

G.Waters

I understand that Debian is not supported OS for SQL server but it had worked until Debian 10 update and the recent update of SQl Server.

So, after Debian update and  before the Server update there was a delay while connection that I described in my previous question.

Now it is an error that makes SQL server completely unusable even for developing or testing.

[ODBC][7284][1565203668.351718][SQLGetConnectAttrW.c][211]Error: SQL_INVALID_HANDLE

Is there a way to fix it or turn off the part of the Server/driver responsible for that error or connect not thru ODBC?

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'

Vinai Kumar Gandla

Hi there, 

I need some DBAs help. 

For security reasons, my organization wants to remove NTService\MSSQLSERVER account from SQL Logins permission.

In this case, do I have to change Service Accounts from 'sql server configuration manager'? and then can I remove it from Login permission? 

If it's possible, could you let me know what I have to refer and which actions do I have to do already? 

And, it's not recommended action, please let me know! 

Thank you in advance. 

Hi,

We are trying to automate the installation process of SQL-server.

The script generates a configurationfile.ini and copies it to the destination server.

Then the script, in short, runs this from our management server:

invoke-command -computername <destionationserver> -scriptblock { F:\setup.exe /configurationfile=C:\temp\configurationfile.ini}

What I have noticed is that if the configurationfile.ini contains AD-accounts as serviceaccounts for the engine and agent. The remote installation fails with the error:

"""

There was an error generating the XML document.

The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.

"""

If the configurationfile.ini contains regular Local system accounts as service accounts for the engine and agent then it works fine.

BUT, if I log in to the destionation server with RDP and then run the script from the management server with AD-accounts as service accounts, it works!

Does anybody have a solution for this? Can delegation in AD be used to solve this? Can you not install SQL server remotely with powershell?

In the end we would like it to work with a service account in AD to run this script from an automation service (like orchestrator).

Thanks!
/Daniel

Hello!

My company has a SQL 2016 Standard not licensed yet, they are negociating a license to activate it, but the server is runing today at evaluatin (180 days) mode. My question is, there is a some kind of processor core limitation at evaluation? 

I runned a heavy query then seeing the Server (2012 R2) processor monitoring and it seems the SQL proccess is using only one processor core/thread, but the server (VMWARE VM) has 4 cores/threads.

Is there a limitation on the evaluation period?

Thanks!

I have SQL server management studio (SQL server 2005) running on windows server 2003 R2. I am upgrading it to windows server 2019. Can I still run the SQL 2005 in windows server 2019?