Hello,

I am purchasing a new SQL server that will have fast SSD SAS 12Gbps drives and I would like to create one RAID10 - 1.6TB partition. MS still recommends separating the data and log files on different disks for SQL 2017, but just wondering if there is still performance improvements by separating data and log files.

What is the best option for performance?

1. One RAID 10 array with one partition?

2. One RAID 10 array with two partitions - one partition includes OS and data and one partition for log files.

3. One RAID 10 array with three partitions - one partition for OS, one partition for data and one partition for log files.

4. Two or three RAID 10 arrays with a partition for each - OS, data and log files.

Thanks!

When trying to install the Visual Studio isolated shell (which I need to install SSMS 17), I am continually getting the same error:

setup engine the process cannot access the file because it is being used by another process

I have NO idea how this is possible when there is nothing running on this laptop. No visual studio, no SQL Server, no SSMS, no SSDT.

How a setup cannot access it's own setup file while it's installing is beyond me.

I have scoured MSDN forums and cannot fins an answer. I have been trying to get my development tools installed on this NEW laptop now for two days and am getting absolutely nowhere.

There is no antivirus running, no firewall, and no other installs running.

Out of options. Has anyone else run into this?

Thanks

A. M. Robinson

Hi everyone,

I'm trying to do a windows update on a server and I get all the time the following error:

Installation Failure: Windows failed to install the following update with error 0x80070643: Microsoft SQL Server 2014 Service Pack 2 (KB3171021).

I've also tried to install manually this SQLServer2014SP2-KB3171021-x64-ENU , but no luck (it freezes on the start of the installation)

Can anyone help on this?

Regards,

Tim Ribeiro

1) I have 2+ hardware hosts with vmware virtualization, and i have 3 virtual MS SQL servers. Can i migrate all 3 MS SQL servers on one hardware host and use only one MS SQL enterprice licence for 3 separated MS SQL servers. Or i need to buy 3 MS SQL licence for each MS SQL server?

2) Also do i need a licence for test-servers. 

Hi there, 

So can I use VS2017 for BizTalk development or is it still VS2015?

Kind regards, 

Peter

Hi Everyone,

       I installed the evaluation a month ago and it installed Enterprise. I need the Standard version because that's what we'll be using when the evaluation ends. I'd rather not uninstall and reinstall when we get the license. Thank you for your assistance!

Jim

Hi,

We're having a SQL Server Standard Edition installed on the machine and would like to know that if it has any expiry date? I tried to find the expiry date but it shows me only installation date and log file also not having any expiry date. 

I believe that SQL Server Standard Edition does not have any expiry date. 

Please help, if it has then how to check the expiry date in the machine.

Padam

Hello,

We are getting the following errors in our SQL Server 2016 servers. These messages are filled in error log. 

2018-07-25 14:21:48.070 spid124s     SSBDT: Dialog timer delete during registration (did: CB9C71C8-93CB-4AE6-B92E-B237A7AE4C67:Initiator, OpType: CloseDialog OpResult: Null)
2018-07-25 14:21:48.080 spid124s     SSBDT: Dialog timer delete during registration (did: 9EDAD00A-90EE-4C0E-925B-DD3258580CE1:Initiator, OpType: CloseDialog OpResult: Null)
2018-07-25 14:22:07.160 spid124s     SSBDT: Dialog timer delete during registration (did: B59E1EB3-D8B7-45EB-82C4-D6145838414F:Initiator, OpType: CloseDialog OpResult: Null)
2018-07-25 14:22:15.730 spid124s     SSBDT: Dialog timer delete during dispatch (did: 039E621C-B0DB-48FE-8B3E-0B09ECE8104B:Target, OpType: DialogCleanupDispatch OpResult: Null)
2018-07-25 14:22:15.760 spid124s     SSBDT: Dialog timer delete during dispatch (did: 7CD4A466-4F9C-404A-9210-A3B4CE2F520D:Target, OpType: DialogCleanupDispatch OpResult: Null)

These may may informational message but not sure these messages are related to which object or process. Error log getting filled. How to stop these message ?

Thanks

Selva

Regards,

The transaction log file of my TempDB does not allow to establish unlimited growth neither for graphic environment nor for transact SQL.

I select the "Unlimited" option but it reappears limited to 2,097,152 bytes

How do I make growth unlimited?

Hi,

Using the setup wizard and configure the SQL Server Databse Engine to use domain account and cheking the checkbox: "Grant Perform Volume Maintenance Task to SQL Server Database Engine Service"

ConfigurationFile.ini:
....
SQLSVCACCOUNT="<domain>\<user>"
; Set to "True" to enable instant file initialization for SQL Server service. If enabled, Setup will grant Perform Volume Maintenance Task privilege to the Database Engine Service SID. This may lead to information disclosure as it could allow deleted content to be accessed by an unauthorized principal.
...

The Setup does not grant the privilege to the configured domain account, instead NT SERVICE\MSSQLSERVER is granted the permission.

Regards,
Brynjar

Hi,

I keep getting the infamous generic error 

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (.Net SqlClient Data Provider)

when trying to connect (from my machine) to an SQL Server located at another machine within the private network.

I've already tried all the obvious and well-known solutions, with no success. From other computers using the same network I can connect without any problems, so it's probably something on my machine.

The weird thing is I work with that server for years and never had this problem, started a few weeks ago, without me changing any configuration. And even more weird is that I can ping the machine normally, the DNS is caching its name and after multiple sequential pings, it suddenly connects. Then, after some minutes of inactive, the error is thrown again.

Can anybody help me with that?

Thanks.

Hi everyone!

  Once bought a SQL Server 2017 copy, is it possible to register its key on an evaluation copy or do I have to reinstall all the software again on the server? Hope I was clear enough. 

Doria

Hi 

I found the error during upgrade SQL Server 2012 SP4 ( Error code 0x84B20002). Please, the detail as below.



The SQL server 2012 installed on Windows server 2012 R2. Could you please recommend me, how to resolve this issue and can update SQL SP4. 

Thank you

Arkom

Hello All,

I have a Database available in SQL Server 2012 environment. I would like to migrate existing Database into the Azure Portal (Azure SQL Database).

Can anyone suggest me the steps or a good reference to continue?

Many Thanks to all of you.

I had SQL 2008 Server. I did <g class="gr_ gr_115 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" data-gr-id="115" id="115">In-Place</g> upgrade to SQL 2014. All the user DBs were in Read-Only mode. After upgrading I see all the DBs are in "Recovery-Pending" mode. I saw the following error msg:

2018-12-07 08:31:05.070 spid19s      Converting database 'XXX' from version 655 to the current version 782.
2018-12-07 08:31:05.070 spid19s      Error: 928, Severity: 20, State: 1.
2018-12-07 08:31:05.070 spid19s      During upgrade, database raised exception 3415, severity 16, state 1, address 00007FFE038AD7D2. Use the exception number to determine the cause.
2018-12-07 08:31:05.080 spid19s      Error: 3415, Severity: 16, State: 1.
2018-12-07 08:31:05.080 spid19s      Database 'XXX' cannot be upgraded because it is read-only, has read-only files or the user does not have permissions to modify some of the files. Make the database or files writeable, and rerun recovery.

How to fix this issue? I don't have any good backup. Any help would be highly appreciated. 

Thanks 

I had SQL 2008 Server. I did In-Place upgrade to SQL 2014. All the user DBs were in Read-Only mode. After upgrading I see all the DBs are in "Recovery-Pending" mode. I saw the following error msg:

2018-12-07 08:31:05.070 spid19s      Converting database 'XXX' from version 655 to the current version 782.
2018-12-07 08:31:05.070 spid19s      Error: 928, Severity: 20, State: 1.
2018-12-07 08:31:05.070 spid19s      During upgrade, database raised exception 3415, severity 16, state 1, address 00007FFE038AD7D2. Use the exception number to determine the cause.
2018-12-07 08:31:05.080 spid19s      Error: 3415, Severity: 16, State: 1.
2018-12-07 08:31:05.080 spid19s      Database 'XXX' cannot be upgraded because it is read-only, has read-only files or the user does not have permissions to modify some of the files. Make the database or files writeable, and rerun recovery.

How to fix this issue? I don't have any good backup. Any help would be highly appreciated. 

Thanks 

Hi,

I'm trying to install SQL Server 2017 Developer, it's a new laptop. one of the forum mentioned to uninstall VS2017. I did uninstall VS2017, but no luck.

Error log:

Detailed results:
  Feature:                       Data Quality Services
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                Microsoft Visual C++ 2015 Redistributable
  Component error code:          1638
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20181209_005841\VCRuntime140_x64_Cpu64_1.log
  Error description:             VS Shell installation has failed with exit code 1638.
  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=VCRuntime140_x64%40Install%400x1638

  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                Microsoft Visual C++ 2015 Redistributable
  Component error code:          1638
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20181209_005841\VCRuntime140_x64_Cpu64_1.log
  Error description:             VS Shell installation has failed with exit code 1638.
  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=VCRuntime140_x64%40Install%400x1638

  Feature:                       Machine Learning Services (In-Database)
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                Microsoft Visual C++ 2015 Redistributable
  Component error code:          1638
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20181209_005841\VCRuntime140_x64_Cpu64_1.log
  Error description:             VS Shell installation has failed with exit code 1638.
  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=VCRuntime140_x64%40Install%400x1638

  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                Microsoft Visual C++ 2015 Redistributable
  Component error code:          1638
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20181209_005841\VCRuntime140_x64_Cpu64_1.log
  Error description:             VS Shell installation has failed with exit code 1638.
  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=VCRuntime140_x64%40Install%400x1638

  Feature:                       SQL Server Replication
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                Microsoft Visual C++ 2015 Redistributable
  Component error code:          1638
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20181209_005841\VCRuntime140_x64_Cpu64_1.log
  Error description:             VS Shell installation has failed with exit code 1638.
  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=VCRuntime140_x64%40Install%400x1638

Please help me to resolve the issue.

Thanks,

info2m

First I had the 1638 exit code problem. I deleted VC++ 2017, yet i have 2005,2008,2012,2013 installed.

On the next try i get the 'The system cannot find the path specified' error

How it can be fixed ? Here is the summary from the last try.

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2147467259
  Start time:                    2017-10-07 15:20:05
  End time:                      2017-10-07 15:21:40
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


Machine Properties:
  Machine name:                  KOLCHAKOV-PC
  Machine processor count:       4
  OS version:                    Microsoft Windows 10 Pro (10.0.15063)
  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
  SQL Server 2017      SQLEXPRESS           MSSQL14.SQLEXPRESS             Database Engine Services                 1033                Express Edition      14.0.1000.169   No         Yes       
  SQL Server 2017      SQLEXPRESS01         MSSQL14.SQLEXPRESS01           Database Engine Services                 1033                Express Edition      14.0.1000.169   No         Yes       

Package properties:
  Description:                   Microsoft SQL Server 2017 
  ProductName:                   SQL Server 2017
  Type:                          RTM
  Version:                       14
  SPLevel:                       0
  Installation location:         C:\SQLServer2017Media\Express\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\20171007_151922\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:                    SQLEXPRESS02
  INSTANCENAME:                  SQLEXPRESS02
  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$SQLEXPRESS02
  SQLSVCINSTANTFILEINIT:         true
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           KOLCHAKOV-PC\nKolchakoV
  SQLTELSVCACCT:                 NT Service\SQLTELEMETRY$SQLEXPRESS02
  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\20171007_151922\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, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x80004005
  Error description:             The system cannot find the path specified
  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=0xF57C3D6F%400xDC80C325&EvtType=0xF57C3D6F%400xDC80C325

Rules with failures:

Global rules:

Scenario specific rules:

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