We tried applying SQL Server 2012 SP4 + Hot fix patch on 2012 SP3 SQL Server. But it didnt allow us to complete the wizard. Error came up in the select features as "There are no sql server instances or shared features that can be updated on this computer". 

SQL Discovery report where SP3 is showing. 

In windows registry & Installed updates, its showing the SP4 updates under SQL Server VSS writer & SQL Server Browser. Where am i missing here ? 

We have a number of servers/instances running 2016.  One of the instances has an issue with SQL Agent jobs, such that for every job history record, there is an error in the error log:

[298] SQLServer Error: 14624, At least one of the following parameters must be specified. "@body, @query, @file_attachments, @subject". [SQLSTATE 42000] (ConnExecuteCachableOp)

Tried:

• Removing all notifications from all jobs, even though they were all configured as failure responses
• Changing the "Include body..." selection
• Changing "Enable mail profile" selection
• Deleted and recreated mail account and mail profile

...however the issue persists.

Tried removing the mail configuration from SQL Server, but that just changes the error:

[298] SQLServer Error: 14636, No global profile is configured. Specify a profile name in the @profile_name parameter. [SQLSTATE 42000] (ConnExecuteCachableOp)

Any help would be appreciated.

I recently upgraded from SSMS 2008 R2, to SSMS 2014. 

I downloaded  the SP3 update for 2008, and ran the install. I think install 2014, utlizing the upgrade option.

The upgrade appeared to work, and DB opens in SSMS2014

The problem I am running into is that, I am attempting to upgrade a software that runs a Pre-checker to ensure the server meets the required specs, and SQL is at the very least on 2014.

When the Pre-checker runs, it indicates that SQL does not meet the minimum. I called the company who owns the pre-chcker and they said it's a windows issue.

I am curious what would cause windows to still think SMS 2008 R2 as being the the primary, even though 2014 has been installed. 

Is there a registry key, or something I need to do to make 2014 be the primary

Hi,

I'm having an issue when starting my mssql-server.service on Linux.

The following error message is generated:

sqlservr: Unable to read instance id from /var/opt/mssql/.system/instance_id: Success (0)
This program has encountered a fatal error and cannot continue running at Wed May 15 12:24:22 2019
The following diagnostic information is available:

Reason: 0x00000003
Message: Unexpected call to legacy ABI.
Stacktrace: 000055c1f94c6464 000055c1f94c5fdf 000055c1f940a66e
               000055c1f9457977
Process: 23721 - sqlservr
Thread: 23722
Instance Id:
Crash Id:
Build stamp: 70437f6583b8ef39b1ef70539ef84690980315dc7a4436c9c40015f28610e4aa
Distribution: Ubuntu 16.04.6 LTS
Processors: 4
Total Memory: 12598861824 bytes
Timestamp: Wed May 15 12:24:22 2019
Aborted (core dumped)

Does anybody know what is wrong, and why i get this error message?

Any help is appreciated

I have a specific scenario to ask questions; however, my goal to identify the general requirement or best practice when upgrading major version or service pack.


We want to upgrade SQL Server 2016 SP1 (GDR "Train") to SQL Server 2017 Latest CU (CU15).  We will perform New Installation with Migration Upgrade.

The questions are as follows, please indicate as well ALL that apply as well a) REQUIRED b) BEST PRACTICE c) NOT REQUIRED d) NOT RECOMMENDED:

1. Should we perform mini-upgrade/CU Patch IN PLACE for SQL Server 2016 SP1 (GDR "Train) to SQL Server 2016 SP2 latest CU (CU7)PRIOR TO Migration Upgrade?

2. If yes to above, should we apply latest CU on SQL Server 2016 SP1 (GDR "Train") prior to SQL Server 2016 SP2 mini-upgrade?

PLEASE EXPLAIN?

Don't forget to apply a-d from above for each question.

Hi,

I'm trying to install SQL Server 2017 Express Edition, just the basic configuration, and I'm getting the following error when I do so.

Oops...

Unable to install SQL Server (setup.exe).

Exit code (Decimal): -2061893607Error description: Could not find the Database Engine startup handle.

I check the Detail.txt file in the setup log folder and see the following possibly relevant lines:

How do I resolve this?

We merged with another company; both sides have their own SQL Servers in different locations and data centers.

Before the Domain Trust was in place, people from both sides were accessing to other side's databases with SQL Server Authentication (temporary solution).

Now the Domain Trust is established, and we can use Windows Authentication (will be the long term, permanent solution) to connect and pull data from each other's SQL Servers.

The issues is.... connecting with Windows Auth is about eight times slow, and pulling data is at least three times slow compared with SQL Authentication.

Any idea why it is so, and any idea how we can make Windows Authentication as fast as SQL Authentication.

Thank you for your help.

Hello,

I have one of the full versions of SQL Server 2014 installed (not sure how to tell exactly which, but definitely a paid one), and want to upgrade to a newer version. I'm a developer, so am eligible to use the free developers edition, but would like to completely replace my existing installation with the new one.

Is this possible? Previous experience with trying to uninstall SQL Server was not pretty. I've tried it a few times (not on this machine), and never managed to get it off completely, so when I tried to install a newer version, it wanted an instance name, and wouldn't let me install is as the default instance.

Anyone able to advise? Thanks

I have been working with SQL for years as a program.  Until my most recent job ALL databases on server I had seen were in one instance.  At my current job each database is in it's own instance.

In all instances there were about 5-6 databases at the most.

Question is which is correct or best?

I am about to move everything from a 2008 server to the newest server and if this is bad I have a good opportunity to correct it.

Thanks,

Derrell Gore

In windows clustering you can run a "Cluster Validation Report" either from the Cluster Administration Console or from PowerShell using Test-Cluster.

However, the output is an .htm file, which isn't really super helpful compared to getting a list of True/False values like you would expect from a "proper" PowerShell cmdlet 

So, my question is whether anyone knows of a way to pass the results from Test-Cluster on, so I can build something that can fix the settings that failed?
Or do I really only have a choice between inventing the wheel by creating a bunch of tests myself, or manually reading a report?

I find it hard to really believe that this is something that hasn't been automated yet?

I have been googling fairly hard, but haven't been able to find any tooling around this already.
(I did suggest fixing our build pipeline so we could have a success-rate higher than 15% on new clusters, but apparently that's not popular ¯\_(ツ)_/¯)

ps. currently I'm looking at whether I can parse the htm file that is output, but meh -__-

I have been looking all over the place for some related info regarding SQL Server 2012's support for Windows Server 2016 but have been unable to find any information so far.

Does anyone know if SQL Server 2012 with SP3 is officially supported on Windows Server 2016? I need to create an instance of SQL Server 2012 running preferably on Windows Server 2016. As much as I'd like to use the newer version of SQL Server (2014, 2016), at this stage I am not able to do it. The Vendor (as of now) certifies the software only for SQL Server 2012 SP2+ or Oracle. I'd would dearly like to avoid Oracle if possible :-). 

I know that I can use Windows Server 2012 R2, but the sysadmins are keen on using Windows Server 2016 if possible. 

Thanks

Hey

Today I startet having problems connecting to my SQL Server on a linux instance from SSMS

It trows this error:

"A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (.Net SqlClient Data Provider)"

Anybody knows how to fix this?

Hi Team,

Could you kindly share me the SQL server 2016 standard edition installation package?

I have tried with the below link but it is not working getting error. attached the error screenshot

https://www.microsoft.com/en-in/evalcenter/evaluate-sql-server-2016

Kindly help me on this. Thanks in advance.

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)