We have upgraded to Windows 10 on a machine running SQL Server 2008 R2 Express.

After upgrading the SQL Server Service will not run automatically and has to be started manually from the services tool.

Same applies after a reboot, you have to run it manually even though the service is set to run automatically.

Is there a fix for this?

Are you able to connect to SQL Management studio after service is started ? if so backup the things and do a fresh install after upgrade and restore the DB's to see if issue get fixed

Are you able to connect to SQL Management studio after service is started ? if so backup the things and do a fresh install after upgrade and restore the DB's to see if issue get

Simon can you share the contents of errorlog here we can see that why it is not coming online. Please share the latest one

Program Files\Microsoft SQL Server\MSSQL.10\MSSQL\LOG\ERRORLOG and ERRORLOG.10 files.

ERRORLOG

• Proposed as answer by Naomi N 14 hours 29 minutes ago
• Unproposed as answer by Naomi N 10 hours 18 minutes ago

I am having the same issue (as well as others) following upgrading to Windows 10 Professional and using SQL server 2014 BI.

This upgrade has been a huge hassle.

Not just 2008 then, there must be a ix for this or a workaround to get the service to start up automatically again

Is it a permission issue or something?

• Proposed as answer by Naomi N Friday, July 31, 2015 4:37 PM
• Unproposed as answer by Naomi N Friday, July 31, 2015 8:49 PM

• Proposed as answer by Naomi N Friday, July 31, 2015 4:37 PM
• Unproposed as answer by Naomi N Friday, July 31, 2015 8:49 PM

Hello,

SQL Server 2008 and SQL Server 2008 R2 are not supported on Windows 10 as mentioned on the following Microsoft Support article:

https://support.microsoft.com/en-us/kb/2681562

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

• Proposed as answer by Naomi N 10 hours 19 minutes ago
• Unproposed as answer by Simon Walton 10 hours 18 minutes ago

Hello,

SQL Server 2008 and SQL Server 2008 R2 are not supported on Windows 10 as mentioned on the following Microsoft Support article:

https://support.microsoft.com/en-us/kb/2681562

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

• Proposed as answer by Naomi N Friday, July 31, 2015 8:48 PM
• Unproposed as answer by Simon Walton Friday, July 31, 2015 8:49 PM

Hello,

SQL Server 2008 and SQL Server 2008 R2 are not supported on Windows 10 as mentioned on the following Microsoft Support article:

https://support.microsoft.com/en-us/kb/2681562

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

• Proposed as answer by Naomi N Friday, July 31, 2015 8:48 PM
• Unproposed as answer by Simon Walton Friday, July 31, 2015 8:49 PM

ERRORLOG

2015-07-31 11:25:42.66 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) 
Apr  2 2010 15:48:46 
Copyright (c) Microsoft Corporation
Data Center Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )

2015-07-31 11:25:42.66 Server      (c) Microsoft Corporation.
2015-07-31 11:25:42.66 Server      All rights reserved.
2015-07-31 11:25:42.66 Server      Server process ID is 6396.
2015-07-31 11:25:42.66 Server      System Manufacturer: 'Acer', System Model: 'Aspire V3-571'.
2015-07-31 11:25:42.66 Server      Authentication mode is WINDOWS-ONLY.
2015-07-31 11:25:42.66 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.PROFORM_RACING\MSSQL\Log\ERRORLOG'.
2015-07-31 11:25:42.66 Server      This instance of SQL Server last reported using a process ID of 6160 at 31/07/2015 00:57:46 (local) 30/07/2015 23:57:46 (UTC). This is an informational message only; no user action is required.
2015-07-31 11:25:42.66 Server      Registry startup parameters: 
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.PROFORM_RACING\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.PROFORM_RACING\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.PROFORM_RACING\MSSQL\DATA\mastlog.ldf
2015-07-31 11:25:42.70 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-07-31 11:25:42.70 Server      Detected 8 CPUs. This is an informational message; no user action is required.
2015-07-31 11:25:42.87 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2015-07-31 11:25:42.90 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-07-31 11:25:42.92 spid6s      Starting up database 'master'.
2015-07-31 11:25:42.97 spid6s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-07-31 11:25:43.08 spid6s      Resource governor reconfiguration succeeded.
2015-07-31 11:25:43.08 spid6s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-07-31 11:25:43.08 spid6s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-07-31 11:25:43.08 spid6s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'PROFORM_RACING'.
2015-07-31 11:25:43.13 spid6s      SQL Trace ID 1 was started by login "sa".
2015-07-31 11:25:43.13 spid6s      Starting up database 'mssqlsystemresource'.
2015-07-31 11:25:43.17 spid6s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2015-07-31 11:25:43.39 spid10s     Starting up database 'model'.
2015-07-31 11:25:43.39 spid6s      Server name is 'PHERNU\PROFORM_RACING'. This is an informational message only. No user action is required.
2015-07-31 11:25:43.40 spid6s      Informational: No full-text supported languages found.
2015-07-31 11:25:43.40 spid6s      Starting up database 'msdb'.
2015-07-31 11:25:43.45 Server      A self-generated certificate was successfully loaded for encryption.
2015-07-31 11:25:43.45 Server      Server is listening on [ 'any' <ipv6> 56607].
2015-07-31 11:25:43.45 Server      Server is listening on [ 'any' <ipv4> 56607].
2015-07-31 11:25:43.45 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\PROFORM_RACING ].
2015-07-31 11:25:43.45 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$PROFORM_RACING\sql\query ].
2015-07-31 11:25:43.45 Server      Server is listening on [ ::1 <ipv6> 56608].
2015-07-31 11:25:43.46 Server      Server is listening on [ 127.0.0.1 <ipv4> 56608].
2015-07-31 11:25:43.46 Server      Dedicated admin connection support was established for listening locally on port 56608.
2015-07-31 11:25:43.46 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2015-07-31 11:25:43.46 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2015-07-31 11:25:43.55 spid10s     Clearing tempdb database.
2015-07-31 11:25:43.97 spid10s     Starting up database 'tempdb'.
2015-07-31 11:25:44.12 spid11s     The Service Broker protocol transport is disabled or not configured.
2015-07-31 11:25:44.12 spid11s     The Database Mirroring protocol transport is disabled or not configured.
2015-07-31 11:25:44.13 spid11s     Service Broker manager has started.
2015-07-31 11:25:44.13 spid6s      Recovery is complete. This is an informational message only. No user action is required.
2015-07-31 11:26:28.39 spid51      Starting up database 'PRODB'.
2015-07-31 11:26:29.27 spid51      CHECKDB for database 'PRODB' finished without errors on 2010-11-17 23:03:16.113 (local time). This is an informational message only; no user action is required.
2015-07-31 12:07:59.63 spid1s      A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 87936, committed (KB): 1279944, memory utilization: 6%.

Did you posted complete message  ??

As per this message SQL server came online. You must apply SQL Server 2008 SP4 you can do that even if SQL Server is stopped after this try starting. I can see 2008 r2 is not supported but it would not stop SQL Server from coming online

At the moment it is difficult getting the right information form the customers so we have a live support session on Monday with one of them to try determine why the service won't start up.

After this I will post up the info we get.

ok, I have upgrade a laptop from windows 7 to windows 10 with SQL Server Express 2008 R2 on it and got the same problem

After boot up SQL server service does not start up

Here are the event view details

Event id 7000

You can get more detail online at this link http://www.microsoft.com/products/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=10.0.10240.16384&EvtID=7000&EvtSrc=Service%20Control%20Manager&FileVer=10.0.10240.16384&FileName=&EvtType=&LCID=1033

Any ideas why it is not starting anyone?

Have you read the article Alberto posted? https://support.microsoft.com/en-us/kb/2681562

=>

For SQL Server 2008 R2

For SQL Server 2008

Yes I understand that but the upgrade checker tool did not say there would be any issues, which it should knowing that 2008 is installed.

I still think there must be a simplier way to get the service to start at startup without re-installing SQL Server 2008

Have you read the article Alberto posted? https://support.microsoft.com/en-us/kb/2681562

=>

For SQL Server 2008 R2

SQL Server 2008 R2 is not supported on Windows 10.

For SQL Server 2008

SQL Server 2008 is not supported on Windows 10.

ok I have found out how to fix it so it starts on startup

Open services by searching for services in the windows 10 search box
Scroll down to the SQL Service that is not starting up
Right Click and choose properties
Change the startup type from Automatic to Automatic (Delayed Start)
Click OK

Restart your computer and the SQL Service will startup at reboot again.

• Proposed as answer by Naomi N Monday, August 03, 2015 3:58 PM

For everybody

I spoke to MS guys today and SQL Server 2008 and 2008 R2 both can run on windows 10 although this is unsupported. If SQL service is not coming online there must be some other issue. Saying that they are not supported and that is why it is not coming online is incorrect.