Forum Discussion
I resolved this problem, howaver this method is not very good.
I think that time that MSSQL service takes to start don't assosiated with MSDTC.
Because sql service take long time to start with MSDTC service group too.
I sql server logs:
2015-05-27 12:03:04.96 spid15s Starting up database 'tempdb'.
2015-05-27 12:04:23.24 Server Using 'dbghelp.dll' version '4.0.5'
2015-05-27 12:04:23.25 Server ***Unable to get thread context for spid 0
2015-05-27 12:04:23.25 Server * *******************************************************************************
2015-05-27 12:04:23.25 Server *
2015-05-27 12:04:23.25 Server * BEGIN STACK DUMP:
2015-05-27 12:04:23.25 Server * 05/27/15 12:04:23 spid 18200
2015-05-27 12:04:23.25 Server *
2015-05-27 12:04:23.25 Server * Non-yielding Scheduler
2015-05-27 12:04:23.25 Server *
2015-05-27 12:04:23.25 Server * *******************************************************************************
2015-05-27 12:04:23.25 Server Stack Signature for the dump is 0x000000000000028A
2015-05-27 12:04:25.03 Server External dump process return code 0x20000001.
External dump process returned no errors.
2015-05-27 12:04:25.03 Server Process 0:0:0 (0x31bc) Worker 0x000000886D802160 appears to be non-yielding on Scheduler 47. Thread creation time: 13077190981781. Approx Thread CPU Used: kernel 60765 ms, user 8468 ms. Process Utilization 4%. System Idle 99%. Interval: 70507 ms.
2015-05-27 12:05:25.42 Server Process 0:0:0 (0x31bc) Worker 0x000000886D802160 appears to be non-yielding on Scheduler 47. Thread creation time: 13077190981781. Approx Thread CPU Used: kernel 113250 ms, user 15531 ms. Process Utilization 4%. System Idle 99%. Interval: 132687 ms.
2015-05-27 12:06:25.81 Server Process 0:0:0 (0x31bc) Worker 0x000000886D802160 appears to be non-yielding on Scheduler 47. Thread creation time: 13077190981781. Approx Thread CPU Used: kernel 165828 ms, user 22250 ms. Process Utilization 4%. System Idle 99%. Interval: 193080 ms.
2015-05-27 12:07:26.18 Server Process 0:0:0 (0x31bc) Worker 0x000000886D802160 appears to be non-yielding on Scheduler 47. Thread creation time: 13077190981781. Approx Thread CPU Used: kernel 218109 ms, user 29312 ms. Process Utilization 4%. System Idle 99%. Interval: 253452 ms.
2015-05-27 12:08:26.59 Server Process 0:0:0 (0x31bc) Worker 0x000000886D802160 appears to be non-yielding on Scheduler 47. Thread creation time: 13077190981781. Approx Thread CPU Used: kernel 270578 ms, user 35843 ms. Process Utilization 4%. System Idle 99%. Interval: 313854 ms.
2015-05-27 12:09:26.96 Server Process 0:0:0 (0x31bc) Worker 0x000000886D802160 appears to be non-yielding on Scheduler 47. Thread creation time: 13077190981781. Approx Thread CPU Used: kernel 322640 ms, user 42406 ms. Process Utilization 4%. System Idle 99%. Interval: 374241 ms.
2015-05-27 12:10:27.32 Server Process 0:0:0 (0x31bc) Worker 0x000000886D802160 appears to be non-yielding on Scheduler 47. Thread creation time: 13077190981781. Approx Thread CPU Used: kernel 374234 ms, user 49250 ms. Process Utilization 4%. System Idle 99%. Interval: 434603 ms.
2015-05-27 12:11:27.70 Server Process 0:0:0 (0x31bc) Worker 0x000000886D802160 appears to be non-yielding on Scheduler 47. Thread creation time: 13077190981781. Approx Thread CPU Used: kernel 425906 ms, user 55984 ms. Process Utilization 4%. System Idle 99%. Interval: 494981 ms.
2015-05-27 12:12:28.07 Server Process 0:0:0 (0x31bc) Worker 0x000000886D802160 appears to be non-yielding on Scheduler 47. Thread creation time: 13077190981781. Approx Thread CPU Used: kernel 476703 ms, user 63359 ms. Process Utilization 4%. System Idle 99%. Interval: 555349 ms.
2015-05-27 12:12:38.26 spid25s The Service Broker endpoint is in disabled or stopped state.
The SQL server start "BEGIN STACK DUMP, Non-yielding Scheduler", this process take 8 minuts. As a result SQL server take 10.30 minuts to start. I didn't resolve problem with sql yet, But I expant SQLonline timeout (SQLserver agent) and SQL can wait sql server now.
Maybe this will help somebody.
Related Content
- 6 days ago
- 9 months ago
- 2 years ago