i tried to install sql server 2008r2 , 2008r2 slipsteam

or even 2014 std on windows 7 x64 ultimate

i got error message at the end of setup:  The request is not supported

details.txt content:

sendspace.com/file/eeqpxa

After upgrading to SQL Server 2016 Enterprise SP2 the following Windows services are failing to start.  This is installed on a Windows 2016 server.

    SQL Server CEIP service (SQLTELEMETRY$InstanceName)

    SQL Server Integration Services CEIP service 13.0 (SSISTELEMETRY130)

Getting this message in Windows Logs....

*--------------------------------------------------------------------------*

Application: sqlceip.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
   at Microsoft.Cloud.Sql.Analytics.BoxTelemetry.AppInsightTelemetrySink..cctor()

Exception Info: System.TypeInitializationException
   at Microsoft.Cloud.Sql.Analytics.BoxTelemetry.AppInsightTelemetrySink..ctor(Microsoft.Cloud.Sql.Analytics.BoxTelemetry.MachineInfo, System.String)
   at Microsoft.Cloud.Sql.Analytics.BoxTelemetry.BoxTelemetry.TelemetryCollectorMain(Microsoft.Cloud.Sql.Analytics.BoxTelemetry.BoxTelemetryOptions)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

Faulting application name: sqlceip.exe, version: 13.0.5026.0, time stamp: 0x5aae92aa
Faulting module name: KERNELBASE.dll, version: 10.0.14393.2457, time stamp: 0x5b7e2adb
Exception code: 0xe0434352
Fault offset: 0x0000000000033c58
Faulting process id: 0xf68
Faulting application start time: 0x01d46a304dcb8e11
Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL13.SCCM\MSSQL\Binn\sqlceip.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: d0bb4b84-20d0-49a8-80b4-6b8b9636bc26
Faulting package full name: 
Faulting package-relative application ID: 

*-----------------------------------------------------------------------------------------*

Any thoughts on this?  These services were fine prior to SP2.

John

Hi!

I have migrated Oracle-tables to SQL Server using SSMA. First I did the migration to the master database and then I made the same migration to a new database I had created with default settings. The migration to the new database failed but the migration to the master database was ok.

The problem was an unique index violation. The column (varchar) had values with only trailing blanks that differs ("ABC" and "ABC "). As it was not a problem in the master database I presume it's a setting in the database, but I don't know which setting it is.

Where is the setting that makes SQL Server regard "ABC" and "ABC " as different values?

Good afternoon,

When using Management Studio for SQL Server 2016 (development environment), the compatibility level defaults to 2008 (level 100) when I attempt to create a brand new database. I check another 2016 instance on another server and this doesn't happen. Does anyone have any idea why this occurs?

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

I am currently working on SQL server up-gradation project from SQL2014(compatibility - 100) to SQL2017(compatibility - 140). Here is one of the challenges i face with respect to behavioural changes b/w the older and newer versions of the DB.

Scenario#1: 

• Insert records into temp table with specific order 

select * into #temp from tblRefUserTypesTest order by UserTypeCode 

• Select and view the records inserted in temp table, 

select * from #temp     

While running this query in 2014, we see that the records are retrieved the same way as they are inserted,ie, in the ascending order of UserTypeCode. But in 2017, it is not so. Though I use 'order by' while inserting the records in the temp table, the select statement does not throw the results as expected, until and unless we use'order by' explicitly in the select statement. I would like to know as to why this behavioral difference occurs due to change in compatibility. Also please let us know as to what type of other issues might face as a result of this compatibility migration.

Hello,

Since two months I can see many entries with the below sentences in SQL logs.

2017-04-24 22:01:43.900 spid31s      SSBDT: Dialog timer delete during registration (did: 725D87C0-8AAF-4383-BCFC-725AC025CD1D:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:02:41.290 spid31s      SSBDT: Dialog timer delete during registration (did: 6F5BF516-934A-45E4-B1B1-D60DF3401B4E:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:03:17.650 spid31s      SSBDT: Dialog timer delete during registration (did: F044EE94-7203-4FF5-9BB6-00D21B86E686:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:03:22.350 spid31s      SSBDT: Dialog timer delete during registration (did: 0B92D137-915C-4920-9C69-541F87266D90:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:03:37.980 spid31s      SSBDT: Dialog timer delete during registration (did: 958A51D1-B18F-410F-93B5-358D10C81EF5:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:03:40.310 spid31s      SSBDT: Dialog timer delete during registration (did: 14373439-9330-4E2C-BF2B-6901A3ED42BF:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:07:39.000 spid31s      SSBDT: Dialog timer delete during registration (did: 6E9C57B7-BDD5-42BC-BA9A-A5A3F97DC91A:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:08:02.360 spid31s      SSBDT: Dialog timer delete during registration (did: 98B47642-1373-4EF7-86B0-E320B48611A9:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:08:02.480 spid31s      SSBDT: Dialog timer delete during registration (did: 1D1263CE-151D-4C64-90BA-4293A29D6BD0:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:09:27.750 spid31s      SSBDT: Dialog timer delete during registration (did: C7D98CCF-F67D-450B-870B-0242585E9B07:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:09:36.700 spid31s      SSBDT: Dialog timer delete during registration (did: 0D243BC3-6B83-45A0-AF2B-E4AF24098B9D:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:09:51.270 spid31s      SSBDT: Dialog timer delete during registration (did: 4CCDA7EA-FB1E-44C7-9234-C0D7C8484750:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:10:15.450 spid31s      SSBDT: Dialog timer delete during registration (did: 2A515B80-9AFA-45F2-9ECB-1328BBB63852:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:11:10.770 spid31s      SSBDT: Dialog timer delete during registration (did: 9920B4CC-EF38-4A8C-A3AE-FAADD7D75267:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:11:15.610 spid31s      SSBDT: Dialog timer delete during registration (did: 4ABA0501-7CD2-4F58-9B59-49A7A9799092:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:11:20.960 spid31s      SSBDT: Dialog timer delete during dispatch (did: 8FAECCF7-6AC5-4FB2-84DC-4927E839D028:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:13:24.770 spid31s      SSBDT: Dialog timer delete during registration (did: A932AF41-C0D0-4234-899B-5E5A4565F924:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:13:24.910 spid31s      SSBDT: Dialog timer delete during registration (did: 00F178A3-640D-44E4-9C39-A69271B279C9:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:13:42.310 spid31s      SSBDT: Dialog timer delete during dispatch (did: 20D9F06E-BC29-4BA5-9623-E08765B42BC7:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:14:00.290 spid31s      SSBDT: Dialog timer delete during registration (did: AA47FA4F-F793-4D89-BBCB-2E434596476F:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:16:31.660 spid31s      SSBDT: Dialog timer delete during registration (did: DD35C46C-7EF0-410F-B78D-CB38DFBD4DEB:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:17:06.290 spid31s      SSBDT: Dialog timer delete during registration (did: E857E323-ED31-4FEC-9AB9-39115D50CA4E:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:18:47.130 spid31s      SSBDT: Dialog timer delete during registration (did: CEDC4256-B4F2-4844-B2DA-9F49C41DE529:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:19:06.390 spid31s      SSBDT: Dialog timer delete during registration (did: 2ACDA3E2-4449-46A8-8A64-E8DF072FEF2A:Initiator, OpType: CloseDialog OpResult: Null)
2017-04-24 22:21:30.410 spid31s      SSBDT: Dialog timer delete during dispatch (did: E09596A9-CD56-4597-B428-DE392D542E29:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:22:32.890 spid31s      SSBDT: Dialog timer delete during dispatch (did: EC39EEE2-ACC5-49F4-A375-2CC3EA2C68CD:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:23:01.630 spid31s      SSBDT: Dialog timer delete during dispatch (did: DF7D37D2-C4C6-403B-AD77-EC070EC47F36:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:23:25.520 spid31s      SSBDT: Dialog timer delete during dispatch (did: 8FDB1B72-8C0B-49F3-B305-93DC9F52EC72:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:25:22.860 spid31s      SSBDT: Dialog timer delete during dispatch (did: 8E7E1C64-16C7-4BB9-A77C-717B1BDF5859:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:25:45.920 spid31s      SSBDT: Dialog timer delete during dispatch (did: E47E8924-8741-48B0-BB55-2B573247CEE7:Target, OpType: DialogCleanupDispatch OpResult: Null)
2017-04-24 22:27:17.560 spid31s      SSBDT: Dialog timer delete during dispatch (did: CBE4F1C7-A98D-424E-AD0D-339727F76937:Target, OpType: DialogCleanupDispatch OpResult: Null)

We are using SQL server 2012 SP3

Do you know what could be the source of that problem?

We could not find info....

Hi,

I am getting following error while installing SQL Server 2017 on Linux SUSE 12 with SP2.

:/> sudo zypper addrepo -r https://packages.microsoft.com/config/sles/12/mssql-server-2017.repo

Download (curl) error for 'https://packages.microsoft.com/config/sles/12/mssql-server-2017.repo':
Error code: Curl error 60
Error message: SSL certificate problem: self signed certificate in certificate chain

Please suggest how to resolve this ?

Thanks,

Hi All,

I installed CU KB4462923 on my production 2008R2 SQL servers on OS Window server 2012R2 and rebooted the servers but the SQL services won't start again after that. But the SQL services starts when I uninstalled the KB4462923. Below are the errors that I'm seeing on my system log:

1) Log Name:      Application

Source:        MSSQLSERVER

Date:          10/22/2018 11:10:06 AM

Event ID:      17120

Task Category: Server

Level:         Error

Keywords:      Classic

User:          N/A

Computer:     

Description:

SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

2)

Log Name:      Application

Source:        MSSQLSERVER

Date:          10/22/2018 11:10:06 AM

Event ID:      17826

Task Category: Server

Level:         Error

Keywords:      Classic

User:          N/A

Computer:     

Description:

Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

3)

Log Name:      Application

Source:        MSSQLSERVER

Date:          10/22/2018 11:10:06 AM

Event ID:      17182

Task Category: Server

Level:         Error

Keywords:      Classic

User:          N/A

Computer:     

Description:

TDSSNIClient initialization failed with error 0x80090331, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The client and server cannot communicate, because they do not possess a common algorithm.

Can someone please help me with solutions or workaround for this errors? I need to figure out how to install this KB without breaking SQL server.

I cannot get past this support rule when I attempt to install SQL Server 2008 RC0.  When I attempt to drill into the failure the popup states "The SQL Server registry keys from a prior installation cannot be modified.  To continue, see SQL Server Setup documentation about how to fix registry keys."

First off, why would the SQL Server 2008 RC0 install attempt to modify registry keys from a prior installation if I am attempting to install it side-by-side with a prior install of SQL Server 2005 Developer Edition?  

Second, can anyone point me to the SQL Server Setup documentation that walks me through how to go about fixing these registry keys?

Any help would be greatly appreciated.  Thanks in advance for your help.

Wendell G

SQL Server 2008R2 Installation is failing with below error, Please advise to troubleshoot the issue.

Vinai Kumar Gandla

Hello, 

We are considering a pilot of SQL Server 2019 CTP 2.0.  <g class="gr_ gr_191 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" data-gr-id="191" id="191">One</g> the biggest things we want to test with this pilot is the extended Polybase functionality with other data sources, such as Oracle and SAP HANA.  Does anyone know or have experience with the following and can provide me feedback:

• Does SQL 2019 CTP2.0 Polybase connect to SAP HANA?
• Are there any potential issues connecting to an SAP HANA instance that is running on SAP Cloud?
• Has anyone connected SQL 2019 CTP 2.0 Polybase to an Oracle SAP ECC 6.0 database?  Any problems or feedback?

Any information would be greatly appreciated!

Thanks,

Kent

I'm trying to install SQL server on my windows 7 workstation and got this error:

A MOF syntax error occured.

I looked in the SQL setup bootstrap folder and found the detail.txt. It says:

(01) 2015-11-29 19:23:58 Slp: Installing WMI Provider
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to open registry subkey 
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\110
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to get registry value SharedCode
(01) 2015-11-29 19:23:58 Slp: SharedDirPath is C:\Program Files (x86)\Microsoft SQL Server\110\Shared\
(01) 2015-11-29 19:23:58 Slp: Attempting to install MOF/MFL file for WMI Provider C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to install MOF file
(01) 2015-11-29 19:23:58 Slp: Running: C:\Windows\system32\WBEM\mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof"
(10) 2015-11-29 19:23:59 Slp: Microsoft (R) MOF Compiler Version 6.1.7600.16385
(10) 2015-11-29 19:23:59 Slp: Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
(10) 2015-11-29 19:24:00 Slp: Parsing MOF file: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof
(10) 2015-11-29 19:24:00 Slp: MOF file has been successfully parsed
(10) 2015-11-29 19:24:00 Slp: Storing data in the repository...
(10) 2015-11-29 19:24:03 Slp: An error occurred while processing item 10 defined on lines 73 - 79 in file C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof:
(10) 2015-11-29 19:24:03 Slp: Compiler returned error 0x80070005Error Number: 0x80070005, Facility: Win32
(10) 2015-11-29 19:24:03 Slp: Description: Access is denied.
(10) 2015-11-29 19:24:03 Slp: 
(01) 2015-11-29 19:24:03 Slp: Sco: Compile operation for mof file C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof failed. Exit code 3
(01) 2015-11-29 19:24:03 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2015-11-29 19:24:03 Slp: A MOF syntax error occurred.
(01) 2015-11-29 19:24:03 Slp: The configuration failure category of current exception is ConfigurationFailure
(01) 2015-11-29 19:24:03 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2015-11-29 19:24:04 Slp: Microsoft.SqlServer.Configuration.Sco.ScoException: A MOF syntax error occurred.
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_ConfigWMIProvider(Dictionary`2 actionData)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_PostMSI(Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2015-11-29 19:24:04 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2015-11-29 19:24:04 Slp: Inner exceptions are being indented
(01) 2015-11-29 19:24:04 Slp: 
(01) 2015-11-29 19:24:04 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(01) 2015-11-29 19:24:04 Slp:     Message: 
(01) 2015-11-29 19:24:04 Slp:         A MOF syntax error occurred.
(01) 2015-11-29 19:24:04 Slp:     HResult : 0x84bb0001
(01) 2015-11-29 19:24:04 Slp:         FacilityCode : 1211 (4bb)
(01) 2015-11-29 19:24:04 Slp:         ErrorCode : 1 (0001)
(01) 2015-11-29 19:24:04 Slp:     Data: 
(01) 2015-11-29 19:24:04 Slp:       SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2015-11-29 19:24:04 Slp:       WatsonConfigActionData = INSTALL@CONFIGNONRC@COMMONFILES
(01) 2015-11-29 19:24:04 Slp:       WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2015-11-29 19:24:04 Slp:     Stack: 
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_ConfigWMIProvider(Dictionary`2 actionData)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_PostMSI(Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2015-11-29 19:24:04 Slp: Watson Bucket 1 
 Original Parameter Values 

(01) 2015-11-29 19:24:04 Slp: Parameter 0 : SQL Server 2012@RTM@ 

(01) 2015-11-29 19:24:04 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof 

(01) 2015-11-29 19:24:04 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof 

(01) 2015-11-29 19:24:04 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1 

(01) 2015-11-29 19:24:04 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1 

(01) 2015-11-29 19:24:04 Slp: Parameter 5 : Slp_Config_Install_Core_WMI_Provider 

(01) 2015-11-29 19:24:04 Slp: Parameter 6 : INSTALL@CONFIGNONRC@COMMONFILES 

(01) 2015-11-29 19:24:04 Slp: 
 Final Parameter Values 

(01) 2015-11-29 19:24:04 Slp: Parameter 0 : SQL Server 2012@RTM@ 

(01) 2015-11-29 19:24:04 Slp: Parameter 1 : 0xA60E3551 

(01) 2015-11-29 19:24:04 Slp: Parameter 2 : 0xA60E3551 

(01) 2015-11-29 19:24:04 Slp: Parameter 3 : 0xD3BEBD98@1211@1 

(01) 2015-11-29 19:24:04 Slp: Parameter 4 : 0xD3BEBD98@1211@1 

(01) 2015-11-29 19:24:04 Slp: Parameter 5 : Slp_Config_Install_Core_WMI_Provider 

(01) 2015-11-29 19:24:04 Slp: Parameter 6 : 0x4E91350D 

(01) 2015-11-29 19:24:06 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
(01) 2015-11-29 19:24:12 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2015-11-29 19:24:50 Slp: A MOF syntax error occurred.
(01) 2015-11-29 19:24:50 Slp: Watson bucket for exception based failure has been created
(01) 2015-11-29 19:38:42 Slp: Error: Action "Slp_Config_Install_Core_WMI_Provider_Cpu64" failed during execution.
(01) 2015-11-29 19:38:42 Slp: Completed Action: Slp_Config_Install_Core_WMI_Provider_Cpu64, returned False

How do I rectify this? Grateful for your advice.

Hi!

I've just built a 2 node Azure 2016 HA always on cluster and its all working except for 1 thing. I can connect via ssms to both instances using the instance names, but the listener name (AG-TmProd) does not connect... 

Im not sure what I've missed..  Any ideas?

Thanks,

Zoe

BACKUP DATABASE testdb  TO DISK = 'C:\testdb.BAK' WITH STATS, 
DESCRIPTION = 'Full backup for AdventureWorks' 
GO 

We have SQL Server 2012 Standard License, Now we need to upgrade it to SQL Server 2017. Is it possible ??

Dear Sir

In order  to imroving backup performance i am using MAXTRANSFERSIZE,BUFFERCOUNT  and  BLOCKSIZE parameter in below Command. w.r.t it I have 2 question.

1. If I run below command than these parameter value ( MAXTRANSFERSIZE,BUFFERCOUNT  and  BLOCKSIZE ) will used for this session only. It will not impact on other job/Server?

2.  Where I can see BLOCKSIZE value. Is it realy work. I mean can we change BLOCKSIZE for particular session as mention below.

DBCC TRACEON (3605,-1)
DBCC TRACEON (3213,-1)

BACKUP DATABASE [TST_DB] TO
DISK = 'D:\DBA\back1.bak',
DISK = 'D:\DBA\OSAK\back2.bak',
DISK = 'D:\DBA\OSAK\back3.bak',
DISK = 'D:\DBA\OSAK\back4.bak',
DISK = 'D:\DBA\OSAK\back5.bak'
with name = 'Backup_ABC', NOINIT,

MAXTRANSFERSIZE = 2097152,
BUFFERCOUNT = 50,
BLOCKSIZE = 8192,

NOSKIP, NOFORMAT   , COMPRESSION, STATS = 5
DBCC TRACEOFF(3605,-1)
DBCC TRACEOFF(3213,-1)

Please suggest me if there any other way to improve backup inconsistency.

Regards,

Deepak

Hello,

Trying to deploy SQL Server 2016 on a maschine that already has SQL Server Mgmt Studio 2017 (v14.0.17277.0) installed. This leads to an exception during installation: 

(01) 2018-10-12 13:25:04 Slp: Target package: "C:\WINDOWS\ccmcache\n\1033_ENU_LP\x64\setup\x86\DACFramework.msi"
(01) 2018-10-12 13:25:04 Slp: MSI Error: 0 A newer version of Microsoft SQL Server Data-Tier Application Framework is already installed.
(01) 2018-10-12 13:25:04 Slp: InstallPackage: MsiInstallProduct returned the result code 1603.

Indeed, the machine has SQL Server Data-Tier Application Framework x86 v14.0.4079.2 already installed during setup of SSMS 2017.

Reproduced this by: 

• uninstalling SSMS 2017
• uninstalling Data-Tier Application Framework
• rebooting
• installing SSMS 2017 again
• > this brings back the data tier application framework v14

When I uninstall the framework and then retry setup for SQL Server 2016, the installation completes successfully.

This creates the following questions for me: 

• is it generally not supported to install SQL Server 2016 when SSMS 2017 is already installed?
• can I somehow prevent SSMS 2017 from installing Data Tier Application Framework?
• can I tell SQL Server 2016 to ignore teh fact that a newer version of Data Tier Application Framework is already installed?