hi there:

  I am using ini to install 2016 developer 

complete syntax below:

setup.exe /ConfigurationFile="C:\SQL2016\ConfigurationFile.ini" /IACCEPTSQLSERVERLICENSETERMS="True"

however, it erroed out with txt below:

  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068578301
  Exit facility code:            1204
  Exit error code:               3
  Exit message:                  The setting 'TROPENLICENSETERMS' specified is not recognized.
  Start time:                    2018-08-30 15:06:39
  End time:                      2018-08-30 15:06:41
  Requested action:              Install

However , I googled around but it's hard to find any information related to this settions: TROPENLICENSETERMS

any ideas? thanks

Hui

---

--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Can I install SQL Server 2014 Standard on Core i3 8100 x64 processor as manual states this:

Processor Type
x64 Processor: AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T support, Intel Pentium IV with EM64T support
x86 Processor: Pentium III-compatible processor or faster.

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

I have a problem and I don't know what is the best solution.

I have set up Always On Availability Group with 2 nodes on SQL Server 2017. Default server collation of the previous sql server (2005) was "SQL_Latin1_General_CP1256_CI_AS". I used "Arabic_CI_AS" as server collation which results in conflict between user databases' collation and tempDB collation.

I don't know if it's better to:

1- Change the server collation to "SQL_Latin1_General_CP1256_CI_AS"

or

2- Change user database collation to "Arabic_CI_AS"

I red some instructions to change server collation on Always On AG and it seems i have to remove Listener and AG (Which i prefer not to). But I couldn't find any instruction to change the database collation in Always On AG.

I Appreciate your help as it's the production server and we have some problems in our software due to his conflict.

Could anyone from Microsoft confirm that the mainstream support end date for SQL Server 2012 SP4 was 11 July 2017?

---

Thanks! Josh

I am creating a sql server failover cluster but during installation I am getting following error:

The cluster resource 'Type='IP Address' NetworkName='Cluster Network 1' Group='SQL SERVER (SQLCLUSTERNEW)' Resource='SQL IP Address 1 (SQLCLUSTERNEW)'' could not be brought online.  Error: The parameter is incorrect.

When I checked the failover cluster manager on one of the cluster node. the failover cluster is being shown offline under cluster core resources. When I tried to bring the cluster online it throws error as : Failed to bring the resource 'Cluster name online. The resource failed to come online due to the failure of one or more provider resources. Please help. How do I solve this issue?

I've been looking around to see if I can find some opinions on accessing SQL management studio directly via the server it is installed on(where the databases are) vs installing a local copy to a desktop and then logging into the databases via object explorer.
I've worked in different places that use different options, and I assumed the reasons are largely based on the clients preference/hosting of servers. However I wondered if there were any actual pros and cons around the two different options that can make one preferable;
ie. is one a more secure option? Are certain things impossible to set up locally?

I find object explorer very convenient for switching between databases and servers, and being able to set things up as registered servers more so.
Obviously if there is anything outside of SQL that requires server access I still have to log on so it may not always be quicker, but I'm interested in hearing what others think.

Are the same SPs and CUs used for updating SQL Server 2016 Developer Edition and SQL Server 2016 Enterprise edition? Before installing Developer Edition in our Dev/Test environment, we want to be sure that when we apply the SPs or CUs to the Developer Edition servers, the same changes are installed when we apply them to the Enterprise edition production environments.

In our organization we have a current setup of 1 sql server in DC connected to a domain controller in DC. for Implementing DR we have a server in DR connected to another domain controller in DR. The systems in DC and DR are in different subnet but same domain and two different domain controllers. I need a procedure or guide in setting up active active sync between the nodes in DC and DR. Any additional resource required? Also if any one can help me in setting up the DC-DR setup; it will be a great help.

As the title says i keep getting the unauthorized operation error, i have looked at several forums before writing here, if anyone has any insight on how to fix it please let me know.

Also i am new to this forum i know you probably need a log file to help me find the error, but i am not sure how to upload the text from the document since the document is so long trying to copy paste crashes my browser.

but have an idea that this part of it might help

(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to get registry value SQL_Engine_Core_Inst
(01) 2018-09-06 10:20:58 Slp: Action "SLP_SQL_Dumper_install_postmsi_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: SLP_SQL_Dumper_install_postmsi_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "SQLDumper_install_postmsi_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: SQLDumper_install_postmsi_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "SQLServerSCP_install_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: SQLServerSCP_install_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_ConfigNonRC_postmsi" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_ConfigNonRC_postmsi, the condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to get instance feature flag UpgradeIncomplete for feature MPT_AGENT_CORE_CNI, instance MSSQL14.MSSQLSERVER08, machine name MALTHELAPTOP
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine MALTHELAPTOP
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to open registry subkey 
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL14.MSSQLSERVER08\UpgradeIncompleteState
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to get registry value MPT_AGENT_CORE_CNI
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to get feature configuration state for feature MPT_AGENT_CORE_CNI, instance MSSQL14.MSSQLSERVER08
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to get instance feature flag ConfigurationState for feature MPT_AGENT_CORE_CNI, instance MSSQL14.MSSQLSERVER08, machine name MALTHELAPTOP
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine MALTHELAPTOP
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to open registry subkey 
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL14.MSSQLSERVER08\ConfigurationState
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to get registry value MPT_AGENT_CORE_CNI
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to set feature configuration state FailedConfigured for feature MPT_AGENT_CORE_CNI, instance MSSQL14.MSSQLSERVER08
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to set instance feature flag ConfigurationState for machine , feature MPT_AGENT_CORE_CNI, instance MSSQL14.MSSQLSERVER08
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to open registry subkey 
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL14.MSSQLSERVER08\ConfigurationState
(01) 2018-09-06 10:20:58 Slp: Sco: Attempting to set value MPT_AGENT_CORE_CNI
(01) 2018-09-06 10:20:58 Slp: SetValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL14.MSSQLSERVER08\ConfigurationState, Name = MPT_AGENT_CORE_CNI
(01) 2018-09-06 10:20:58 Slp: Action "AgentInstall_AgentInitializeSettings_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: AgentInstall_AgentInitializeSettings_Cpu64, the condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "AgentInstall_AgentInitializeRuntimeSettings_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: AgentInstall_AgentInitializeRuntimeSettings_Cpu64, the condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "AgentInstall_AgentCalculateInstallNonRC_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: AgentInstall_AgentCalculateInstallNonRC_Cpu64, the condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "AgentInstall_AgentInstallNonRC_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: AgentInstall_AgentInstallNonRC_Cpu64, the condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_ConfigRC_postmsi" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_ConfigRC_postmsi, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "SlpLegacyDiscovery_install_ConfigRC_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: SlpLegacyDiscovery_install_ConfigRC_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "SqlEngineDBStartConfigAction_install_configrc_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: SqlEngineDBStartConfigAction_install_configrc_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "AgentScriptConfiguration_install_rc_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: AgentScriptConfiguration_install_rc_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "RS_RunInstallScriptsAction_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: RS_RunInstallScriptsAction_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "Polybase_Install_CreateConfigDatabasesAction_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: Polybase_Install_CreateConfigDatabasesAction_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "SQL_Telemetry_Install_ConfigRC_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: SQL_Telemetry_Install_ConfigRC_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "SQL_Telemetry_LoginInstall_ConfigRC_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: SQL_Telemetry_LoginInstall_ConfigRC_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "SqlEngineDBStopConfigAction_install_configrc_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: SqlEngineDBStopConfigAction_install_configrc_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_ConfigRC_postmsi" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_ConfigRC_postmsi, the condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "SqlBrowserConfigEngAction_install_Startup_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: SqlBrowserConfigEngAction_install_Startup_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "SqlEngineConfigAction_install_startup_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: SqlEngineConfigAction_install_startup_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "SQL_Telemetry_Install_Startup_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: SQL_Telemetry_Install_Startup_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi, the condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "AgentInstall_AgentInstallStartup_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: AgentInstall_AgentInstallStartup_Cpu64, the condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi, the condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Completed Action: PostMsiTimingConfigAction, returned True
(01) 2018-09-06 10:20:58 Slp: Completed Action: ExecuteStandardTimingsWorkflow, returned True
(01) 2018-09-06 10:20:58 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:20:58 Slp: Running Action: ExecuteExtendedTimingsWorkflow
(01) 2018-09-06 10:20:58 Slp: Workflow to execute: 'EXTENDEDTIMINGS'
(01) 2018-09-06 10:20:58 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:20:58 Slp: Running Action: DowntimeTimingConfigAction
(01) 2018-09-06 10:20:58 Slp: Completed Action: DowntimeTimingConfigAction, returned True
(01) 2018-09-06 10:20:58 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:20:58 Slp: Skipping Action: FinalizePreUpgradeAction
(01) 2018-09-06 10:20:58 Slp: Action is being skipped due to the following restrictions: 
(01) 2018-09-06 10:20:58 Slp: Condition "Is the user's scenario set to Upgrade" did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:20:58 Slp: Running Action: StartupTimingConfigAction
(01) 2018-09-06 10:20:58 Slp: Completed Action: StartupTimingConfigAction, returned True
(01) 2018-09-06 10:20:58 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:20:58 Slp: Running Action: PreUninstallTimingConfigAction
(01) 2018-09-06 10:20:58 Slp: Completed Action: PreUninstallTimingConfigAction, returned True
(01) 2018-09-06 10:20:58 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:20:58 Slp: Running Action: UninstallTimingConfigAction
(01) 2018-09-06 10:20:58 Slp: Completed Action: UninstallTimingConfigAction, returned True
(01) 2018-09-06 10:20:58 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:20:58 Slp: Running Action: UpgradeMsiTimingAction
(01) 2018-09-06 10:20:58 Slp: Completed Action: UpgradeMsiTimingAction, returned True
(01) 2018-09-06 10:20:58 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:20:58 Slp: Running Action: FinalizeTimingConfigAction
(01) 2018-09-06 10:20:58 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Finalize_finalize" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Finalize_finalize, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "cluster_group_cluster_finalconfig_Cpu64" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: cluster_group_cluster_finalconfig_Cpu64, the condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Finalize_finalize" will return false due to the following conditions:
(01) 2018-09-06 10:20:58 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Finalize_finalize, the condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
(01) 2018-09-06 10:20:58 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
(01) 2018-09-06 10:20:58 Slp: Completed Action: FinalizeTimingConfigAction, returned True
(01) 2018-09-06 10:20:58 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:20:58 Slp: Running Action: CreateARPRegKeyAction
(01) 2018-09-06 10:20:58 Slp: Completed Action: CreateARPRegKeyAction, returned True
(01) 2018-09-06 10:20:58 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:20:58 Slp: Running Action: RunRefreshDiscoveryAction
(01) 2018-09-06 10:20:58 Slp: Running discovery on local machine
(01) 2018-09-06 10:21:00 Slp: Discovery on local machine is complete
(01) 2018-09-06 10:21:00 Slp: Completed Action: RunRefreshDiscoveryAction, returned True
(01) 2018-09-06 10:21:00 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:21:00 Slp: Running Action: NotifyProgressComplete
(01) 2018-09-06 10:21:00 Slp: Completed Action: NotifyProgressComplete, returned True
(01) 2018-09-06 10:21:00 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:21:00 Slp: Skipping Action: DeleteUninstalledPatchRegistryAndCacheFolderAction
(01) 2018-09-06 10:21:00 Slp: Action is being skipped due to the following restrictions: 
(01) 2018-09-06 10:21:00 Slp: Condition "Do any of the specified features match the expected scenario Uninstall" did not pass as it returned false and true was expected.
(01) 2018-09-06 10:21:00 Slp: Completed Action: ExecuteExtendedTimingsWorkflow, returned True
(01) 2018-09-06 10:21:00 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:21:00 Slp: Running Action: DeleteUpdates
(01) 2018-09-06 10:21:00 Slp: Deleting folder 'C:\Users\Malthe\AppData\Local\Temp\SQL Server 2017'.
(01) 2018-09-06 10:21:00 Slp: Sco: Directory C:\Users\Malthe\AppData\Local\Temp\SQL Server 2017 does not exist
(01) 2018-09-06 10:21:00 Slp: Completed Action: DeleteUpdates, returned True
(01) 2018-09-06 10:21:00 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:21:00 Slp: Running Action: ExecuteCloseWorkflow
(01) 2018-09-06 10:21:00 Slp: Workflow to execute: 'CLOSE'
(01) 2018-09-06 10:21:00 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:21:00 Slp: Running Action: DetermineProductFeatureSummary
(01) 2018-09-06 10:21:01 Slp: Completed Action: DetermineProductFeatureSummary, returned True
(01) 2018-09-06 10:21:01 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:21:01 Slp: Running Action: ProduceStatusLogs
(01) 2018-09-06 10:21:02 Slp: Completed Action: ProduceStatusLogs, returned True
(01) 2018-09-06 10:21:02 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:21:02 Slp: Running Action: FinalizeProgressStatus
(01) 2018-09-06 10:21:02 Slp: Completed Action: FinalizeProgressStatus, returned True
(01) 2018-09-06 10:21:02 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:21:02 Slp: Running Action: RebootMessageAction
(01) 2018-09-06 10:21:02 Slp: Completed Action: RebootMessageAction, returned True
(01) 2018-09-06 10:21:02 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:21:02 Slp: Skipping Action: FinishPage
(01) 2018-09-06 10:21:02 Slp: Action is being skipped due to the following restrictions: 
(01) 2018-09-06 10:21:02 Slp: Condition "Is the user's scenario set to EditionUpgrade" did not pass as it returned false and true was expected.
(01) 2018-09-06 10:21:02 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:21:02 Slp: Running Action: CloseUI
(01) 2018-09-06 10:21:02 Slp: Stop action skipped in UI Mode Quiet
(01) 2018-09-06 10:21:02 Slp: Completed Action: CloseUI, returned True
(01) 2018-09-06 10:21:02 Slp: Completed Action: ExecuteCloseWorkflow, returned True
(01) 2018-09-06 10:21:02 Slp: Completed Action: ExecuteCompleteWorkflow, returned True
(01) 2018-09-06 10:21:02 Slp: SetupTelemetry: Writing Telemetry to Datastore
(01) 2018-09-06 10:21:04 Slp: 
(01) 2018-09-06 10:21:04 Slp: 
(01) 2018-09-06 10:21:04 Slp: ----------------------------------------------------------------------
(01) 2018-09-06 10:21:04 Slp: 
(01) 2018-09-06 10:21:04 Slp: Error result: -2068119551
(01) 2018-09-06 10:21:04 Slp: Result facility code: 1211
(01) 2018-09-06 10:21:04 Slp: Result error code: 1
(01) 2018-09-06 10:21:04 Slp: WER: Application level consent value 'True' was mapped to consent status 'WerConsentApproved'
(01) 2018-09-06 10:21:05 Slp: WER: Result of the submission:: 'WerReportQueued'
(01) 2018-09-06 10:21:05 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
(01) 2018-09-06 10:21:05 Slp: SetupTelemetry: Closing Telemetry Session
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\SQMClient
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to get registry value MachineId
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\140
(01) 2018-09-06 10:21:05 Slp: SetupTelemetry: Not creating telemetry audit log. Value 'UserRequestedLocalAuditDirectory' doesn't exist in 'HKLM\Software\Microsoft\Microsoft SQL Server\140'
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\140
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to open registry subkey SQL
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to get registry value MSSQLSERVER08
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\MSSQL14.MSSQLSERVER08\CPE
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to open registry subkey OLAP
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
(01) 2018-09-06 10:21:05 Slp: Sco: Attempting to open registry subkey RS
(01) 2018-09-06 10:21:05 Slp: SetupTelemetry: Telemetry has an active session with 46 events.

help me 

it keep notice that: "There are no features selected for upgrade " what should i do for it??

Greetings,

my company is preparing to upgrade SQL Server from 2005/2008 to 2016.

We have a lot of .NET applications whose code contains many SQL instructions (dynamic queries and so on): is there any best practice or tool to check if these instructions are compatible with the new version of SQL Server?

Thank you in advance,

Emiliano.

Good morning!

My user group at the company has been working with SQL Server Management Studio installed locally on our desktops/laptops.  Our database that we connect to is stored on a SQL that we have not been allowed to Remote Desktop into.  This database has moved 4 times in the 2 years that I have been with the company.  Each time we move, we have had to also move the location / ip address of the ONLY folder we have been allowed to bulk load from.  That has required adjustments to some of our code that loads data on a regular basis from that location.  We are going through our 4th move right now and I requested that we leave the location of this alone.  Our IS team is telling us that'simpossible to accomplish with a desktop install.  I am not usually one to second guess but I want to ensure that there is no way to allow a database hosted on a server to access a remote location when the user group is running a desktop install.  That just seems like something that people would want to do with SQL server...

Thanks for any guidance!

I am uninstalling SQL 2014 RTM and it is failing. All of the googling I have done points me to clustered installs and nodes. We do not implement any of that so I am kind of at a loss where to start.

Summary.txt contains this.

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2146233088
  Exit facility code:            19
  Exit error code:               5376
  Exit message:                  Failed to retrieve data for this request.
  Start time:                    2018-09-06 13:37:50
  End time:                      2018-09-06 13:38:02
  Requested action:              Uninstall
  Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xE019508D%400x9C63FDAE&EvtType=0xE019508D%400x9C63FDAE

Machine Properties:
  Machine name:                  LABBK
  Machine processor count:       2
  OS version:                    Windows 7
  OS service pack:               Service Pack 1
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Package properties:
  Description:                   Microsoft SQL Server 2014 
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       0
  Installation edition:          

User Input Settings:
  ACTION:                        Uninstall
  CONFIGURATIONFILE:             
  ENU:                           true
  FEATURES:                      SQL, RS
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  false
  INDICATEPROGRESS:              false
  INSTANCEID:                    <empty>
  INSTANCENAME:                  [redacted]
  QUIET:                         true
  QUIETSIMPLE:                   false
  UIMODE:                        Normal
  X86:                           false

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

Rules with failures:

Global rules:

There are no scenario-specific rules.

Rules report file:               The rule result report file is not available.

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.Management.Sdk.Sfc.EnumeratorException
    Message: 
        Failed to retrieve data for this request.
    HResult : 0x80131500
    Data: 
      HelpLink.ProdName = Microsoft SQL Server
      HelpLink.BaseHelpUrl = http://go.microsoft.com/fwlink
      HelpLink.LinkId = 20476
      DisableWatson = true
    Stack: 
        at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
        at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.ProcessDTbl(DataTable dt, Int32 level)
        at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectSqlDiscoveryData(String machineName)
        at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectDiscoveryData(String machineName)
        at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
        at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    Inner exception type: System.InvalidCastException
        Message: 
                Unable to cast object of type 'System.String' to type 'System.String[]'.
        HResult : 0x80004002
        Stack: 
                at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String machineName, RegistryView regView)
                at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
                at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
                at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
                at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
                at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)

Detail.txt attached.

For an unknown reason the primary replica is synchronized however the secondary replica was not synchronized? This is a database with few changes because it is being used to configure our application servers before we do a final full backup.   The secondary replica was in a restoring mode.  Is this normal?  Could reboots have caused this loss of data?,... please explain why the synchronization is not fixing the lost data? Or is too much data lost.    

When attempting to failover there is a warning of potential data loss.

Error below when clicking on link for replica not synchronizing.   We are using auto synch.   This is two node SQL AG.

How do we fix the below error?  I tried removing the database from the AG then deleted the secondary replica.  Next added the database back into the AG and seeded it automatically.  It finished but the below error occurred?  Synchronization was not occurring on the secondary replica.    

Also noticed when deleted the database from the secondary replica that it removes from the UI however it remains on the local drive.   Could automatic seeding have failed because these data files were there originally??  But there was no error indicating duplicate database files.  In fact the wizard finished.

How do we fix this???    

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Data synchronization state of some availability database is not healthy.

availability database is suspended.

At least one availability database on this availability replica has an unhealthy data synchronization state. If this is an asynchronous-commit availability replica, all availability databases should be in the SYNCHRONIZING state. If this is a synchronous-commit availability replica, all availability databases should be in the SYNCHRONIZED state.

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

---

dsk

Noted that we have to remove a database from a SQL AG before we can restore it?  Why is this required?   Is this because the changes are too much for a AG synch to recover from??

What other scenarios do we need to remove a database from the AG?   Do we have to remove from the AG for some SQL Alter commands?  Is it best practice to remove from AG then add back to AG after running a SQL Alter command?

Do we have to run alter command on the other secondary database if this alter query is run on a database outside the AG?  If this is done how do we add  back to the AG?,... do we use the "Join" option for synchronization.   We used Automatic seeding originally when adding this database originally to the AG however since we already have a secondary database on the secondary replica w local database files on the secondary node.

We removed the database from the AG because a sql query would not run so we ran the query then we add the database back to the AG.  We used the "JOIN" option.  However afterwards the secondary database would not synch with the primary database?   I am NOT understanding the wording used in the wizard for the JOIN option.   Is it saying that you can only use JOIN when the primary database and the secondary database are identical without any differences?,... this means even a Alter broker command could break this synchronization??  

What method do you recommend for adding back to the AG after the SQL alter command is run on a database outside the SQL AG?

---

dsk

During the adding of a database to the AG the second option is "Full database and Log backup" for the Select Initial Data Synchronization step.   

Do we have to perform a full backup and log backup on the database?   It also says "these databases are restored to each secondary and joined to the AG".    Why is both a full backup and a log backup required?   When would we use this option versus the 1st option which is AUTOMATIC seeding??

XXXXXXXXXXXXXXXXXXXX

The 4th option is "Skip initial data synchronization" in the Select Initial Data Synchronization step.   It say to choose this option if you want to perform your own database and log backups of each primary database>>> what does this mean?  When would we choose this option???  

---

dsk

Hi,

is it possible to download the Developer Edition of SQL Server vers. 2014 only as a Visual Studio Dev Essentials member?

Thanks

Hi,

I have install and configured SQL Server 2016, and trying to restore SQL Server 2017 DB on SQL Server 2016 and getting following error:

"The database was backed up on a server running version 14.00.3015 the version is incompatible which is running 13.00.5026"

pls guide what options are available. 

Thx 

---

iffi