Добро пожаловать в форум, Guest  >>   Войти | Регистрация | Поиск | Правила | В избранное | Подписаться
Все форумы / Microsoft SQL Server Новый топик    Ответить
Топик располагается на нескольких страницах: [1] 2 3   вперед  Ctrl      все
 SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
sereban
Member

Откуда:
Сообщений: 38
Возникла проблема из ниоткуда: с какого-то момента пару месяцев назад (не было ни обновлений, ни настроек сервера, ни хрена ничего, плановый перезапуск, чтобы почистилась tempdb) началась такая херня: после перезапуска службы минут через 5 процесс sql сервера начинает жрать оперативную память(230 Гб!!!!! все что ему отведено на сервере), при этом сервер перестает отвечать на запросы. На сервере стоят базы 1с. Но до него нельзя в этот момент достучаться не из 1с не из менеджмент студии. Т.е. проконтролировать что он делает в этот момент не получается. Активность диска в этот момент нулевая. Т.е. ниодна база не читается и ничего никуда не пишется. Процессор загружен 30-50% (4 проца по 4 ядра 1,87ггц). Вот такая херня продолжается 10-15 минут, пока не захватит всю доступную память. Потом он начинает ее освобождать с 230Гб примерно до 30Гб. В этот момент sql уже отвечает на запросы и кое как можно работать в базах, но производительность составляет примерно 10-20% от нормы (замеры отдельных операций сделать не могу, потому что работать в принципе невозможно, т.к. в рабочем режиме сервер нагружен процентов на 70!!!!, а когда такие тормоза возникают, нам приходится отрубать большую часть пользовательских сеансов, чтобы хоть кто-то мог работать). Процесс освобождения памяти идет примерно час. Если оставить на сервере десятую часть пользователей, то работать еще как-то можно. После того как сервер освободит память до 30Гб начинается нормальная работа: производительность приходит в норму, сервер успевает обрабатывать запросы и потихоньку расходует оперативку(+70Гб съедает за 2-3 часа, потом замедляется, за пару дней может выбрать максимально доступные 230). Получается чтобы сервер пришел в рабочее состояние после перезагрузки ему необходимо 1,5 часа времени. Может кто сталкивался? Представить не могу куда копать...
7 май 13, 13:58    [14267650]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
Ozerov
Member

Откуда: Москва
Сообщений: 3637
В логах ничего нет интересного ?
Можно попробовать аудит включить, перегрузить сервер и посмотреть, что происходило.
7 май 13, 14:04    [14267686]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
Гость333
Member

Откуда:
Сообщений: 3683
sereban,

Через DAC тоже не удаётся подключиться?
Использование выделенного административного соединения
7 май 13, 14:18    [14267774]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
sereban
Member

Откуда:
Сообщений: 38
Гость333
sereban,

Через DAC тоже не удаётся подключиться?
Использование выделенного административного соединения


DAC не пробовал (нужно повторить все зло на рабочем сервере), щас копаю журнал. Там проблема не в том, что подключиться не удается, а в том что sql отвечать перестает. Т.е. SSMS была запущена, жму выполнить запрос, а результат увижу только минут через 15 как отвиснит.
7 май 13, 14:29    [14267849]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
tpg
Member

Откуда: Novosibirsk
Сообщений: 23902
А как там с SELECT @@VERSION ?
7 май 13, 14:44    [14267980]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
Glory
Member

Откуда:
Сообщений: 104751
sereban
после перезапуска службы

И как осуществлятся перезапуск ?
С предварительным отключением всех коннектов ?
7 май 13, 14:46    [14268008]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
sereban
Member

Откуда:
Сообщений: 38
tpg
А как там с SELECT @@VERSION ?


Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) Jun 28 2012 08:36:30 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
7 май 13, 15:02    [14268144]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
andrew911
Member

Откуда:
Сообщений: 1
updates ставите вообще на него?
7 май 13, 15:07    [14268200]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
sereban
Member

Откуда:
Сообщений: 38
Glory
sereban
после перезапуска службы

И как осуществлятся перезапуск ?
С предварительным отключением всех коннектов ?


Все соединения это сервер 1с и 1-2 SSMS. Сервер 1с предварительно был остановлен. Потом остановлена служба sql server. После перезагрузки сервера все было запущено в обратном порядке.
7 май 13, 15:08    [14268204]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
aleks2
Guest
sereban
началась такая херня: после перезапуска службы минут через 5 процесс sql сервера начинает жрать оперативную память(230 Гб!!!!! все что ему отведено на сервере), при этом сервер перестает отвечать на запросы. На сервере стоят базы 1с.


Если подключений нет - единственное занятие сервера откатка и закатка транзакций.
Это должно в журнале отражаться.
7 май 13, 15:31    [14268395]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
Критик
Member

Откуда: Москва / Калуга
Сообщений: 35396
Блог
возможно, есть задачи, запланированные на запуск сервера,
но это тоже должно быть в логах
7 май 13, 15:52    [14268555]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
sereban
Member

Откуда:
Сообщений: 38
Никогда раньше не копался в логах sql сервера. Может кто найдет что здесь нитак. И вообще тот ли лог я смотрю?

+
Date,Source,Severity,Message
05/07/2013 16:03:27,spid116,Unknown,Process ID 80 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 15:03:00,spid123,Unknown,Process ID 101 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 14:50:00,spid161,Unknown,Process ID 52 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 14:30:10,spid54,Unknown,Process ID 141 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 12:01:49,spid101,Unknown,Process ID 141 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 12:01:44,spid113,Unknown,Process ID 118 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:36:20,spid174,Unknown,Process ID 90 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:32:35,spid4s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\logs\RNG_Volgograd_log.ldf] in database [RNG_Volgograd] (9). The OS file handle is 0x0000000000000CC8. The offset of the latest long I/O is: 0x0000001a8d6200
05/07/2013 11:28:25,spid4s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\logs\RNG_Obl_Sever_log.ldf] in database [RNG_Obl_Sever] (7). The OS file handle is 0x0000000000000CA4. The offset of the latest long I/O is: 0x00000002593c00
05/07/2013 11:21:57,spid93,Unknown,Process ID 101 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:21:57,spid92,Unknown,Process ID 126 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:21:57,spid98,Unknown,Process ID 238 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:21:57,spid221,Unknown,Process ID 239 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:21:57,spid110,Unknown,Process ID 76 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:21:56,spid111,Unknown,Process ID 100 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:21:56,spid245,Unknown,Process ID 72 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:21:56,spid115,Unknown,Process ID 185 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:21:56,spid245,Unknown,Process ID 67 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:21:56,spid80,Unknown,Process ID 242 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:21:56,spid92,Unknown,Process ID 172 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:21:56,spid98,Unknown,Process ID 146 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:21:56,spid110,Unknown,Process ID 208 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:21:56,spid65,Unknown,Process ID 227 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:21:56,spid68,Unknown,Process ID 228 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:21:56,spid245,Unknown,Process ID 212 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:21:55,spid92,Unknown,Process ID 136 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:21:55,spid52,Unknown,Process ID 113 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:21:55,spid112,Unknown,Process ID 51 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:21:55,spid125,Unknown,Process ID 64 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:21:55,spid125,Unknown,Process ID 84 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:21:55,spid65,Unknown,Process ID 235 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:21:55,spid93,Unknown,Process ID 222 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:21:55,spid114,Unknown,Process ID 215 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:21:55,spid52,Unknown,Process ID 225 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:21:55,spid118,Unknown,Process ID 195 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:21:55,spid230,Unknown,Process ID 231 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:21:55,spid110,Unknown,Process ID 82 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:21:55,spid119,Unknown,Process ID 52 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:21:55,spid78,Unknown,Process ID 236 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:21:55,spid119,Unknown,Process ID 78 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:21:54,spid112,Unknown,Process ID 237 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:21:54,spid234,Unknown,Process ID 218 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:52,spid229,Unknown,Process ID 158 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:52,spid234,Unknown,Process ID 205 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:52,spid172,Unknown,Process ID 126 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:52,spid233,Unknown,Process ID 217 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:52,spid131,Unknown,Process ID 194 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:52,spid172,Unknown,Process ID 253 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:52,spid51,Unknown,Process ID 206 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:52,spid238,Unknown,Process ID 180 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:52,spid233,Unknown,Process ID 132 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:52,spid162,Unknown,Process ID 219 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:52,spid230,Unknown,Process ID 226 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:19:52,spid234,Unknown,Process ID 67 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:52,spid233,Unknown,Process ID 119 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:52,spid228,Unknown,Process ID 69 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:52,spid51,Unknown,Process ID 223 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:52,spid234,Unknown,Process ID 137 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:52,spid238,Unknown,Process ID 154 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:52,spid227,Unknown,Process ID 139 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:52,spid227,Unknown,Process ID 214 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:52,spid244,Unknown,Process ID 193 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:52,spid233,Unknown,Process ID 102 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:52,spid221,Unknown,Process ID 97 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:19:52,spid109,Unknown,Process ID 121 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:51,spid233,Unknown,Process ID 211 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:51,spid185,Unknown,Process ID 248 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:51,spid101,Unknown,Process ID 148 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:51,spid109,Unknown,Process ID 134 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:51,spid131,Unknown,Process ID 80 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:51,spid113,Unknown,Process ID 130 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:51,spid227,Unknown,Process ID 99 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:51,spid228,Unknown,Process ID 209 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:51,spid227,Unknown,Process ID 216 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:51,spid86,Unknown,Process ID 65 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:51,spid233,Unknown,Process ID 107 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:51,spid72,Unknown,Process ID 243 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:51,spid234,Unknown,Process ID 95 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:51,spid185,Unknown,Process ID 183 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:51,spid172,Unknown,Process ID 151 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:51,spid221,Unknown,Process ID 149 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:19:51,spid84,Unknown,Process ID 197 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:51,spid84,Unknown,Process ID 64 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:51,spid185,Unknown,Process ID 190 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:51,spid230,Unknown,Process ID 155 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:19:51,spid172,Unknown,Process ID 207 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:51,spid230,Unknown,Process ID 204 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:19:51,spid244,Unknown,Process ID 232 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:51,spid181,Unknown,Process ID 184 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:51,spid229,Unknown,Process ID 199 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:51,spid229,Unknown,Process ID 68 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:51,spid242,Unknown,Process ID 92 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:51,spid234,Unknown,Process ID 118 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:51,spid244,Unknown,Process ID 202 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:51,spid72,Unknown,Process ID 176 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:51,spid72,Unknown,Process ID 177 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:51,spid242,Unknown,Process ID 153 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:51,spid162,Unknown,Process ID 198 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:51,spid208,Unknown,Process ID 104 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:51,spid229,Unknown,Process ID 201 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:51,spid72,Unknown,Process ID 156 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:51,spid131,Unknown,Process ID 186 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:51,spid221,Unknown,Process ID 220 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:19:51,spid72,Unknown,Process ID 96 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:51,spid131,Unknown,Process ID 88 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:51,spid86,Unknown,Process ID 187 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:51,spid86,Unknown,Process ID 54 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:51,spid93,Unknown,Process ID 200 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:51,spid229,Unknown,Process ID 178 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:51,spid230,Unknown,Process ID 106 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:19:51,spid221,Unknown,Process ID 168 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:19:51,spid233,Unknown,Process ID 74 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:51,spid233,Unknown,Process ID 210 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:51,spid234,Unknown,Process ID 51 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:51,spid113,Unknown,Process ID 175 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:51,spid86,Unknown,Process ID 145 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:51,spid162,Unknown,Process ID 143 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:51,spid229,Unknown,Process ID 129 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:51,spid72,Unknown,Process ID 159 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:51,spid172,Unknown,Process ID 179 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:51,spid172,Unknown,Process ID 70 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:51,spid116,Unknown,Process ID 94 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:19:50,spid230,Unknown,Process ID 125 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:19:50,spid113,Unknown,Process ID 188 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:50,spid113,Unknown,Process ID 147 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:50,spid172,Unknown,Process ID 123 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:50,spid84,Unknown,Process ID 135 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:50,spid208,Unknown,Process ID 98 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:50,spid162,Unknown,Process ID 160 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:50,spid72,Unknown,Process ID 166 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:50,spid162,Unknown,Process ID 252 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:50,spid110,Unknown,Process ID 53 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:50,spid233,Unknown,Process ID 115 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:50,spid242,Unknown,Process ID 203 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:50,spid162,Unknown,Process ID 141 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:50,spid162,Unknown,Process ID 110 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:50,spid93,Unknown,Process ID 128 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:50,spid72,Unknown,Process ID 152 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:50,spid84,Unknown,Process ID 189 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:50,spid111,Unknown,Process ID 72 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:50,spid86,Unknown,Process ID 157 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:50,spid116,Unknown,Process ID 191 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:19:50,spid113,Unknown,Process ID 138 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:50,spid111,Unknown,Process ID 93 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:50,spid86,Unknown,Process ID 196 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:50,spid84,Unknown,Process ID 142 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:50,spid162,Unknown,Process ID 86 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:19:40,spid242,Unknown,Process ID 165 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:19:39,spid136,Unknown,Process ID 163 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:39,spid116,Unknown,Process ID 84 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:19:39,spid113,Unknown,Process ID 111 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:39,spid229,Unknown,Process ID 173 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:39,spid146,Unknown,Process ID 113 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:19:39,spid136,Unknown,Process ID 146 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:19:39,spid213,Unknown,Process ID 241 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:19:39,spid185,Unknown,Process ID 167 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:19:38,spid228,Unknown,Process ID 162 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:38,spid228,Unknown,Process ID 171 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:38,spid228,Unknown,Process ID 133 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:19:38,spid116,Unknown,Process ID 100 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:14:10,spid178,Unknown,Process ID 158 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:13:15,spid78,Unknown,Process ID 175 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:12:47,spid235,Unknown,Process ID 169 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:12:47,spid206,Unknown,Process ID 123 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:12:47,spid102,Unknown,Process ID 53 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:12:47,spid78,Unknown,Process ID 82 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:12:47,spid179,Unknown,Process ID 159 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:12:47,spid235,Unknown,Process ID 212 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:12:47,spid252,Unknown,Process ID 249 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:12:47,spid78,Unknown,Process ID 177 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:12:47,spid129,Unknown,Process ID 80 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:12:47,spid129,Unknown,Process ID 239 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:12:47,spid185,Unknown,Process ID 213 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:12:47,spid114,Unknown,Process ID 140 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:12:47,spid114,Unknown,Process ID 224 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:12:47,spid185,Unknown,Process ID 106 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:12:47,spid125,Unknown,Process ID 68 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:12:47,spid200,Unknown,Process ID 69 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:12:47,spid125,Unknown,Process ID 194 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:12:47,spid138,Unknown,Process ID 54 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:12:47,spid161,Unknown,Process ID 256 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:12:46,spid176,Unknown,Process ID 104 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:12:46,spid180,Unknown,Process ID 128 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:12:46,spid176,Unknown,Process ID 186 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:12:46,spid94,Unknown,Process ID 195 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:12:46,spid125,Unknown,Process ID 247 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:12:46,spid253,Unknown,Process ID 250 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:12:46,spid138,Unknown,Process ID 207 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:12:46,spid94,Unknown,Process ID 52 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:12:46,spid193,Unknown,Process ID 148 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:12:46,spid139,Unknown,Process ID 65 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:12:46,spid131,Unknown,Process ID 258 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:12:45,spid150,Unknown,Process ID 172 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:12:35,spid193,Unknown,Process ID 125 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:36,spid210,Unknown,Process ID 209 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:36,spid119,Unknown,Process ID 238 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:36,spid249,Unknown,Process ID 257 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:36,spid181,Unknown,Process ID 64 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:36,spid119,Unknown,Process ID 53 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:36,spid181,Unknown,Process ID 94 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:36,spid137,Unknown,Process ID 113 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:07:36,spid181,Unknown,Process ID 255 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:36,spid240,Unknown,Process ID 126 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:36,spid240,Unknown,Process ID 141 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:36,spid104,Unknown,Process ID 193 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:36,spid249,Unknown,Process ID 90 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:36,spid240,Unknown,Process ID 155 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:36,spid249,Unknown,Process ID 163 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:36,spid123,Unknown,Process ID 173 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:07:36,spid52,Unknown,Process ID 114 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:07:36,spid200,Unknown,Process ID 184 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:07:36,spid258,Unknown,Process ID 143 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:07:36,spid179,Unknown,Process ID 118 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:07:36,spid200,Unknown,Process ID 225 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:07:36,spid207,Unknown,Process ID 156 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:35,spid215,Unknown,Process ID 93 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:07:35,spid249,Unknown,Process ID 100 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:35,spid104,Unknown,Process ID 70 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:35,spid215,Unknown,Process ID 245 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:07:35,spid132,Unknown,Process ID 217 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:35,spid207,Unknown,Process ID 259 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:35,spid52,Unknown,Process ID 145 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:07:35,spid220,Unknown,Process ID 176 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:07:35,spid207,Unknown,Process ID 226 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:35,spid80,Unknown,Process ID 251 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:35,spid194,Unknown,Process ID 121 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:07:35,spid142,Unknown,Process ID 154 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:07:35,spid207,Unknown,Process ID 98 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:35,spid99,Unknown,Process ID 205 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:07:35,spid185,Unknown,Process ID 197 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:07:35,spid132,Unknown,Process ID 166 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:35,spid249,Unknown,Process ID 147 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:35,spid249,Unknown,Process ID 152 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:35,spid241,Unknown,Process ID 169 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:35,spid76,Unknown,Process ID 254 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:07:35,spid185,Unknown,Process ID 171 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:07:35,spid52,Unknown,Process ID 237 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:07:35,spid195,Unknown,Process ID 107 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:07:35,spid123,Unknown,Process ID 88 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:07:35,spid99,Unknown,Process ID 233 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:07:35,spid92,Unknown,Process ID 219 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:07:35,spid92,Unknown,Process ID 116 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:07:35,spid179,Unknown,Process ID 182 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:07:35,spid179,Unknown,Process ID 161 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:07:35,spid179,Unknown,Process ID 246 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:07:35,spid179,Unknown,Process ID 162 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:07:35,spid207,Unknown,Process ID 190 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:35,spid195,Unknown,Process ID 67 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:07:35,spid195,Unknown,Process ID 201 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:07:35,spid252,Unknown,Process ID 234 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:35,spid240,Unknown,Process ID 218 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:35,spid137,Unknown,Process ID 68 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:07:35,spid252,Unknown,Process ID 244 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:35,spid256,Unknown,Process ID 192 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:07:35,spid200,Unknown,Process ID 199 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:07:35,spid258,Unknown,Process ID 159 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:07:35,spid258,Unknown,Process ID 72 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:07:35,spid220,Unknown,Process ID 78 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:07:35,spid180,Unknown,Process ID 231 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:35,spid80,Unknown,Process ID 110 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:35,spid74,Unknown,Process ID 167 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:35,spid185,Unknown,Process ID 198 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:07:35,spid142,Unknown,Process ID 150 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:07:35,spid180,Unknown,Process ID 187 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:35,spid74,Unknown,Process ID 208 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:35,spid104,Unknown,Process ID 242 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:35,spid256,Unknown,Process ID 227 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:07:34,spid80,Unknown,Process ID 183 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:34,spid259,Unknown,Process ID 129 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:34,spid220,Unknown,Process ID 153 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 11:07:34,spid104,Unknown,Process ID 133 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:34,spid256,Unknown,Process ID 214 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:07:34,spid104,Unknown,Process ID 174 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:34,spid185,Unknown,Process ID 196 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:07:34,spid181,Unknown,Process ID 178 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:34,spid240,Unknown,Process ID 54 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:34,spid212,Unknown,Process ID 86 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:07:34,spid258,Unknown,Process ID 216 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:07:34,spid104,Unknown,Process ID 96 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:33,spid76,Unknown,Process ID 164 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:07:33,spid200,Unknown,Process ID 211 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:07:33,spid76,Unknown,Process ID 131 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:07:33,spid142,Unknown,Process ID 151 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:07:33,spid232,Unknown,Process ID 140 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 11:07:33,spid256,Unknown,Process ID 130 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:07:33,spid80,Unknown,Process ID 170 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:33,spid142,Unknown,Process ID 177 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:07:33,spid101,Unknown,Process ID 222 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:07:33,spid259,Unknown,Process ID 160 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:33,spid142,Unknown,Process ID 115 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:07:29,spid249,Unknown,Process ID 146 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:29,spid82,Unknown,Process ID 181 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:07:29,spid256,Unknown,Process ID 104 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 11:07:26,spid243,Unknown,Process ID 189 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 11:07:25,spid259,Unknown,Process ID 191 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:25,spid157,Unknown,Process ID 135 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 11:07:24,spid142,Unknown,Process ID 84 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 11:07:24,spid258,Unknown,Process ID 138 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 11:07:24,spid259,Unknown,Process ID 204 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 11:07:24,spid220,Unknown,Process ID 102 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 10:55:08,spid64,Unknown,Process ID 97 was killed by hostname H034-SQL-04<c/> host process ID 9164.
05/07/2013 10:54:53,spid54,Unknown,Process ID 159 was killed by hostname H034-SQL-04<c/> host process ID 896.
05/07/2013 10:54:53,spid199,Unknown,Process ID 205 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 10:54:53,spid93,Unknown,Process ID 112 was killed by hostname H034-SQL-04<c/> host process ID 1780.
05/07/2013 10:54:53,spid190,Unknown,Process ID 65 was killed by hostname H034-SQL-04<c/> host process ID 4420.
05/07/2013 10:54:53,spid123,Unknown,Process ID 129 was killed by hostname H034-SQL-04<c/> host process ID 4184.
05/07/2013 10:54:53,spid121,Unknown,Process ID 86 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 10:54:50,spid104,Unknown,Process ID 133 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 10:54:50,spid121,Unknown,Process ID 160 was killed by hostname H034-SQL-04<c/> host process ID 8324.
05/07/2013 10:54:30,spid213,Unknown,Process ID 144 was killed by hostname H034-SQL-04<c/> host process ID 8968.
05/07/2013 10:50:48,spid99,Unknown,Process ID 66 was killed by hostname H034-SQL-04<c/> host process ID 2244.
05/07/2013 10:40:49,Сервер,Unknown,IO Completion Listener (0x1998) Worker 0x0000000005A3C1A0 appears to be non-yielding on Node 0. Approx CPU Used: kernel 0 ms<c/> user 0 ms<c/> Interval: 14859.
05/07/2013 10:40:49,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000000001BF708 : 19<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:49,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x0000000431DB8088 : 12<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:49,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000001ECC702C8 : 25<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:49,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x000000027C5CC2C8 : 10<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:49,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000000C617FB88 : 18<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:20,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x0000000005062E08 : 23<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:49,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x0000000279A102C8 : 32<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:45,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000000C505EBC8 : 3<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:39,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000002795DA748 : 14<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:20,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000003D84C8748 : 27<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:20,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000001E6484748 : 16<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:20,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000003A50B7948 : 20<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:20,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x000000000581C748 : 29<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:20,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000000D2492508 : 28<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000001ED8F0BC8 : 17<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000000CF48B708 : 30<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000003A1F02508 : 21<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x000000042CACE088 : 24<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x000000033BBDB048 : 8<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x0000000431DA8088 : 13<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000000D2A88748 : 15<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x000000030F2382C8 : 31<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000000C617AE08 : 5<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x0000000000513B88 : 9<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x0000000005133048 : 2<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x0000000431DA4088 : 6<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x000000036AAB4988 : 11<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x0000000279A13B88 : 4<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000000008AD4C8 : 7<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:19,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000003DF620748 : 26<c/> waittime 600<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:40:09,Сервер,Unknown,IO Completion Listener (0x1998) Worker 0x0000000005A3C1A0 appears to be non-yielding on Node 0. Approx CPU Used: kernel 2854 ms<c/> user 23883 ms<c/> Interval: 34165.
05/07/2013 10:39:51,Сервер,Unknown,IO Completion Listener (0x1998) Worker 0x0000000005A3C1A0 appears to be non-yielding on Node 0. Approx CPU Used: kernel 811 ms<c/> user 12043 ms<c/> Interval: 14857.
05/07/2013 10:39:22,Сервер,Unknown,IO Completion Listener (0x1998) Worker 0x0000000005A3C1A0 appears to be non-yielding on Node 0. Approx CPU Used: kernel 2870 ms<c/> user 22885 ms<c/> Interval: 34405.
05/07/2013 10:39:21,Вход,Unknown,Login failed for user 'DBA'. Причина: не удалось открыть явно указанную базу данных. [КЛИЕНТ: <named pipe>]
05/07/2013 10:39:21,Вход,Unknown,Ошибка: 18456<c/> серьезность: 14<c/> состояние: 38.
05/07/2013 10:39:04,Сервер,Unknown,IO Completion Listener (0x1998) Worker 0x0000000005A3C1A0 appears to be non-yielding on Node 0. Approx CPU Used: kernel 951 ms<c/> user 11216 ms<c/> Interval: 14859.
05/07/2013 10:38:36,spid132,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 000000043081A3E8<c/> type 4<c/> Task 0x00000000001BFDC8 : 16<c/> waittime 300<c/> flags 0x1a<c/> owning task 0x00000000008E1B88. Continuing to wait.
05/07/2013 10:38:36,spid132,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 000000043081A3E8<c/> type 4<c/> Task 0x0000000005133DC8 : 18<c/> waittime 300<c/> flags 0x1a<c/> owning task 0x00000000008E1B88. Continuing to wait.
05/07/2013 10:37:25,Сервер,Unknown,IO Completion Listener (0x1998) Worker 0x0000000005A3C1A0 appears to be non-yielding on Node 0. Approx CPU Used: kernel 1279 ms<c/> user 9890 ms<c/> Interval: 14671.
05/07/2013 10:37:25,Server,Unknown,External dump process return code 0x20000001.<nl/>External dump process returned no errors.
05/07/2013 10:37:15,Server,Unknown,Stack Signature for the dump is 0x0000000000000253
05/07/2013 10:37:15,Server,Unknown,* Short Stack Dump
05/07/2013 10:37:15,Server,Unknown,* -------------------------------------------------------------------------------
05/07/2013 10:37:15,Server,Unknown,* *******************************************************************************
05/07/2013 10:37:15,Server,Unknown,*
05/07/2013 10:37:15,Server,Unknown,* Non-yielding IOCP Listener
05/07/2013 10:37:15,Server,Unknown,*
05/07/2013 10:37:15,Server,Unknown,* 05/07/13 10:37:15 spid 5968
05/07/2013 10:37:15,Server,Unknown,* BEGIN STACK DUMP:
05/07/2013 10:37:15,Server,Unknown,*
05/07/2013 10:37:15,Server,Unknown,* *******************************************************************************
05/07/2013 10:37:15,Server,Unknown,***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0008.txt
05/07/2013 10:37:15,Server,Unknown,**Dump thread - spid = 0<c/> EC = 0x0000000000000000
05/07/2013 10:37:14,Server,Unknown,Using 'dbghelp.dll' version '4.0.5'
05/07/2013 10:36:33,spid141,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 00000004302463E8<c/> type 4<c/> Task 0x0000000005781048 : 32<c/> waittime 300<c/> flags 0x1a<c/> owning task 0x00000000050EFB88. Continuing to wait.
05/07/2013 10:36:18,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000000D13DEE08 : 22<c/> waittime 300<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:34:08,spid157,Unknown,Failed to run resource governor classifier user-defined function. See previous errors in SQL Server error log from session ID 157 for details. Classifier elapsed time: 21 ms.
05/07/2013 10:34:08,spid157,Unknown,Ошибка: 10982<c/> серьезность: 16<c/> состояние: 1.
05/07/2013 10:23:51,spid55,Unknown,Using 'xplog70.dll' version '2009.100.1600' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
05/07/2013 10:23:51,spid55,Unknown,Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
05/07/2013 10:23:50,spid55,Unknown,Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
05/07/2013 10:23:50,spid55,Unknown,Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
05/07/2013 10:23:50,spid55,Unknown,Using 'xpsqlbot.dll' version '2009.100.1600' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
05/07/2013 10:23:50,spid55,Unknown,Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
05/07/2013 10:23:44,spid6s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
05/07/2013 10:23:44,spid6s,Unknown,Recovery is writing a checkpoint in database 'RNG_Volgograd' (9). This is an informational message only. No user action is required.
05/07/2013 10:23:44,spid6s,Unknown,0 transactions rolled back in database 'RNG_Volgograd' (9). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid19s,Unknown,612 transactions rolled forward in database 'RNG_Volgograd' (9). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid6s,Unknown,Recovery is writing a checkpoint in database 'rng_obl_yug_section' (11). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid6s,Unknown,0 transactions rolled back in database 'rng_obl_yug_section' (11). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid20s,Unknown,1 transactions rolled forward in database 'rng_obl_yug_section' (11). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid11s,Unknown,Service Broker manager has started.
05/07/2013 10:23:43,spid19s,Unknown,Recovery of database 'RNG_Volgograd' (9) is 2% complete (approximately 5 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid19s,Unknown,Recovery of database 'RNG_Volgograd' (9) is 0% complete (approximately 18 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid19s,Unknown,Recovery of database 'RNG_Volgograd' (9) is 0% complete (approximately 23 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid11s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
05/07/2013 10:23:43,spid11s,Unknown,The Service Broker protocol transport is disabled or not configured.
05/07/2013 10:23:43,spid19s,Unknown,Recovery of database 'RNG_Volgograd' (9) is 0% complete (approximately 23 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid22s,Unknown,Recovery is writing a checkpoint in database 'vagan_test' (13). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid22s,Unknown,0 transactions rolled back in database 'vagan_test' (13). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid21s,Unknown,Recovery is writing a checkpoint in database 'For_RNG' (10). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid21s,Unknown,0 transactions rolled back in database 'For_RNG' (10). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid6s,Unknown,Recovery is writing a checkpoint in database 'Test_Vagan' (12). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid6s,Unknown,0 transactions rolled back in database 'Test_Vagan' (12). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid22s,Unknown,1 transactions rolled forward in database 'vagan_test' (13). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid21s,Unknown,485 transactions rolled forward in database 'Test_Vagan' (12). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid14s,Unknown,1 transactions rolled forward in database 'For_RNG' (10). This is an informational message only. No user action is required.
05/07/2013 10:23:43,spid16s,Unknown,Starting up database 'ReportServer'.
05/07/2013 10:23:43,spid20s,Unknown,Starting up database 'rng_obl_yug_section'.
05/07/2013 10:23:43,spid19s,Unknown,Starting up database 'RNG_Volgograd'.
05/07/2013 10:23:43,spid14s,Unknown,Starting up database 'For_RNG'.
05/07/2013 10:23:43,spid21s,Unknown,Starting up database 'Test_Vagan'.
05/07/2013 10:23:43,spid22s,Unknown,Starting up database 'vagan_test'.
05/07/2013 10:23:43,spid15s,Unknown,Starting up database 'RNG_Obl_Sever'.
05/07/2013 10:23:43,spid18s,Unknown,Starting up database 'RNG_Obl_Yug'.
05/07/2013 10:23:43,spid17s,Unknown,Starting up database 'ReportServerTempDB'.
05/07/2013 10:23:43,spid11s,Unknown,Starting up database 'msdb'.
05/07/2013 10:23:43,Сервер,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
05/07/2013 10:23:43,Сервер,Unknown,The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/h034-sql-04.mrg134.mrg.gazprom.ru:1433 ] for the SQL Server service.
05/07/2013 10:23:43,Сервер,Unknown,The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/h034-sql-04.mrg134.mrg.gazprom.ru ] for the SQL Server service.
05/07/2013 10:23:43,Сервер,Unknown,Dedicated admin connection support was established for listening locally on port 1434.
05/07/2013 10:23:43,Сервер,Unknown,Server is listening on [ 127.0.0.1 <ipv4> 1434].
05/07/2013 10:23:43,Сервер,Unknown,Server is listening on [ ::1 <ipv6> 1434].
05/07/2013 10:23:43,Сервер,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
05/07/2013 10:23:43,Сервер,Unknown,Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
05/07/2013 10:23:43,Сервер,Unknown,Server is listening on [ 'any' <ipv4> 1433].
05/07/2013 10:23:43,Сервер,Unknown,Server is listening on [ 'any' <ipv6> 1433].
05/07/2013 10:23:43,Сервер,Unknown,A self-generated certificate was successfully loaded for encryption.
05/07/2013 10:23:43,spid11s,Unknown,A new instance of the full-text filter daemon host process has been successfully started.
05/07/2013 10:23:42,spid10s,Unknown,Starting up database 'tempdb'.
05/07/2013 10:23:42,spid10s,Unknown,Clearing tempdb database.
05/07/2013 10:23:42,spid6s,Unknown,Server name is 'H034-SQL-04'. This is an informational message only. No user action is required.
05/07/2013 10:23:42,spid10s,Unknown,Starting up database 'model'.
05/07/2013 10:23:42,spid6s,Unknown,The resource database build version is 10.50.4000. This is an informational message only. No user action is required.
05/07/2013 10:23:42,spid6s,Unknown,Starting up database 'mssqlsystemresource'.
05/07/2013 10:23:42,spid6s,Unknown,SQL Trace ID 1 was started by login "sa".
05/07/2013 10:23:42,spid6s,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQLSERVER'.
05/07/2013 10:23:42,spid6s,Unknown,SQL Server Audit has started the audits. This is an informational message. No user action is required.
05/07/2013 10:23:42,spid6s,Unknown,SQL Server Audit is starting the audits. This is an informational message. No user action is required.
05/07/2013 10:23:42,spid6s,Unknown,Resource governor reconfiguration succeeded.
05/07/2013 10:23:42,spid6s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
05/07/2013 10:23:42,spid6s,Unknown,0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
05/07/2013 10:23:42,spid6s,Unknown,4 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
05/07/2013 10:23:42,spid6s,Unknown,Starting up database 'master'.
05/07/2013 10:23:42,Сервер,Unknown,Node configuration: node 0: CPU mask: 0x00000000ffffffff:0 Active CPU mask: 0x00000000ffffffff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
05/07/2013 10:23:41,Сервер,Unknown,Lock partitioning is enabled. This is an informational message only. No user action is required.
05/07/2013 10:23:41,Сервер,Unknown,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.
05/07/2013 10:23:40,Server,Unknown,Cannot use Large Page Extensions: lock memory privilege was not granted.
05/07/2013 10:23:40,Сервер,Unknown,Detected 32 CPUs. This is an informational message; no user action is required.
05/07/2013 10:23:40,Сервер,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
05/07/2013 10:23:40,Server,Unknown,Registry startup parameters: <nl/> -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf<nl/> -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG<nl/> -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
05/07/2013 10:23:40,Server,Unknown,This instance of SQL Server last reported using a process ID of 1336 at 07.05.2013 10:17:20 (local) 07.05.2013 6:17:20 (UTC). This is an informational message only; no user action is required.
05/07/2013 10:23:40,Server,Unknown,Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
05/07/2013 10:23:40,Server,Unknown,Authentication mode is MIXED.
05/07/2013 10:23:40,Server,Unknown,System Manufacturer: 'VMware<c/> Inc.'<c/> System Model: 'VMware Virtual Platform'.
05/07/2013 10:23:40,Server,Unknown,Server process ID is 6048.
05/07/2013 10:23:40,Server,Unknown,All rights reserved.
05/07/2013 10:23:40,Server,Unknown,(c) Microsoft Corporation.
05/07/2013 10:23:40,Server,Unknown,Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) <nl/> Jun 28 2012 08:36:30 <nl/> Copyright (c) Microsoft Corporation<nl/> Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)


Событие Process ID *** was killed by hostname - это мы убивали сеансы, которые дольше остальных ожидают ответ от сервера, чтобы хоть как то его разгрузить.
7 май 13, 16:24    [14268945]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
komrad
Member

Откуда:
Сообщений: 5759
привет газпрому

если по делу, у вас похоже на сброс планов и использование параллелизма
покажите

exec sp_configure 'show advanced',1
reconfigure with override
go
exec sp_configure
go


+ у вас не стоит разрешение lock pages in memory для эккаунта под которым работает сиквел

ссылка
7 май 13, 16:44    [14269157]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
Ozerov
Member

Откуда: Москва
Сообщений: 3637
komrad
привет газпрому

если по делу, у вас похоже на сброс планов и использование параллелизма
покажите

exec sp_configure 'show advanced',1
reconfigure with override
go
exec sp_configure
go


+ у вас не стоит разрешение lock pages in memory для эккаунта под которым работает сиквел

ссылка


А разве lock pages in memory нужен не исключительно для AWE ?
7 май 13, 16:52    [14269228]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
--------------------------------
Guest
А это что за фигня?

05/07/2013 10:36:33,spid141,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 00000004302463E8<c/> type 4<c/> Task 0x0000000005781048 : 32<c/> waittime 300<c/> flags 0x1a<c/> owning task 0x00000000050EFB88. Continuing to wait.
05/07/2013 10:36:18,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000000D13DEE08 : 22<c/> waittime 300<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:34:08,spid157,Unknown,Failed to run resource governor classifier user-defined function. See previous errors in SQL Server error log from session ID 157 for details. Classifier elapsed time: 21 ms.
05/07/2013 10:34:08,spid157,Unknown,Ошибка: 10982<c/> серьезность: 16<c/> состояние: 1.
7 май 13, 16:57    [14269278]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
komrad
Member

Откуда:
Сообщений: 5759
Ozerov
komrad
привет газпрому

если по делу, у вас похоже на сброс планов и использование параллелизма
покажите

exec sp_configure 'show advanced',1
reconfigure with override
go
exec sp_configure
go


+ у вас не стоит разрешение lock pages in memory для эккаунта под которым работает сиквел

ссылка


А разве lock pages in memory нужен не исключительно для AWE ?


из лога
05/07/2013 10:23:40,Server,Unknown,Cannot use Large Page Extensions: lock memory privilege was not granted.
7 май 13, 16:58    [14269291]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
komrad
Member

Откуда:
Сообщений: 5759
--------------------------------
А это что за фигня?

05/07/2013 10:36:33,spid141,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 00000004302463E8<c/> type 4<c/> Task 0x0000000005781048 : 32<c/> waittime 300<c/> flags 0x1a<c/> owning task 0x00000000050EFB88. Continuing to wait.
05/07/2013 10:36:18,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000000D13DEE08 : 22<c/> waittime 300<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:34:08,spid157,Unknown,Failed to run resource governor classifier user-defined function. See previous errors in SQL Server error log from session ID 157 for details. Classifier elapsed time: 21 ms.
05/07/2013 10:34:08,spid157,Unknown,Ошибка: 10982<c/> серьезность: 16<c/> состояние: 1.


вероятно ресурс говернер используется

use master
go
-- Get the stored metadata.
select 
object_schema_name(classifier_function_id) as 'Classifier UDF schema in metadata', 
object_name(classifier_function_id) as 'Classifier UDF name in metadata'
from 
sys.resource_governor_configuration
go
-- Get the in-memory configuration.
select 
object_schema_name(classifier_function_id) as 'Active classifier UDF schema', 
object_name(classifier_function_id) as 'Active classifier UDF name'
from 
sys.dm_resource_governor_configuration
go
7 май 13, 17:08    [14269349]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
sereban
Member

Откуда:
Сообщений: 38
komrad
привет газпрому

если по делу, у вас похоже на сброс планов и использование параллелизма
покажите

exec sp_configure 'show advanced',1
reconfigure with override
go
exec sp_configure
go


+ у вас не стоит разрешение lock pages in memory для эккаунта под которым работает сиквел

ссылка


+
access check cache bucket count 0 65536 0 0
access check cache quota 0 2147483647 0 0
Ad Hoc Distributed Queries 0 1 0 0
affinity I/O mask -2147483648 2147483647 0 0
affinity mask -2147483648 2147483647 0 0
affinity64 I/O mask -2147483648 2147483647 0 0
affinity64 mask -2147483648 2147483647 0 0
Agent XPs 0 1 1 1
allow updates 0 1 0 0
awe enabled 0 1 0 0
backup compression default 0 1 0 0
blocked process threshold (s) 0 86400 0 0
c2 audit mode 0 1 0 0
clr enabled 0 1 0 0
common criteria compliance enabled 0 1 0 0
cost threshold for parallelism 0 32767 5 5
cross db ownership chaining 0 1 0 0
cursor threshold -1 2147483647 -1 -1
Database Mail XPs 0 1 0 0
default full-text language 0 2147483647 1033 1033
default language 0 9999 21 21
default trace enabled 0 1 1 1
disallow results from triggers 0 1 0 0
EKM provider enabled 0 1 0 0
filestream access level 0 2 0 0
fill factor (%) 0 100 0 0
ft crawl bandwidth (max) 0 32767 100 100
ft crawl bandwidth (min) 0 32767 0 0
ft notify bandwidth (max) 0 32767 100 100
ft notify bandwidth (min) 0 32767 0 0
index create memory (KB) 704 2147483647 0 0
in-doubt xact resolution 0 2 0 0
lightweight pooling 0 1 0 0
locks 5000 2147483647 0 0
max degree of parallelism 0 1024 0 0
max full-text crawl range 0 256 4 4
max server memory (MB) 16 2147483647 230000 230000
max text repl size (B) -1 2147483647 65536 65536
max worker threads 128 32767 0 0
media retention 0 365 0 0
min memory per query (KB) 512 2147483647 1024 1024
min server memory (MB) 0 2147483647 0 0
nested triggers 0 1 1 1
network packet size (B) 512 32767 4096 4096
Ole Automation Procedures 0 1 0 0
open objects 0 2147483647 0 0
optimize for ad hoc workloads 0 1 0 0
PH timeout (s) 1 3600 60 60
precompute rank 0 1 0 0
priority boost 0 1 0 0
query governor cost limit 0 2147483647 0 0
query wait (s) -1 2147483647 -1 -1
recovery interval (min) 0 32767 0 0
remote access 0 1 1 1
remote admin connections 0 1 0 0
remote login timeout (s) 0 2147483647 20 20
remote proc trans 0 1 0 0
remote query timeout (s) 0 2147483647 0 0
Replication XPs 0 1 0 0
scan for startup procs 0 1 0 0
server trigger recursion 0 1 1 1
set working set size 0 1 0 0
show advanced options 0 1 1 1
SMO and DMO XPs 0 1 1 1
SQL Mail XPs 0 1 0 0
transform noise words 0 1 0 0
two digit year cutoff 1753 9999 2049 2049
user connections 0 32767 2048 2048
user options 0 32767 0 0
xp_cmdshell 0 1 0 0
7 май 13, 17:14    [14269386]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
Ozerov
Member

Откуда: Москва
Сообщений: 3637
из лога
05/07/2013 10:23:40,Server,Unknown,Cannot use Large Page Extensions: lock memory privilege was not granted.


Крайне странно... Может там AWE, до кучи, включен ?... Никогда не использовал на х64 системах этот параметр (проверил на всяк) и никаких проблем.
7 май 13, 17:15    [14269391]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
sereban
Member

Откуда:
Сообщений: 38
komrad
--------------------------------
А это что за фигня?

05/07/2013 10:36:33,spid141,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 00000004302463E8<c/> type 4<c/> Task 0x0000000005781048 : 32<c/> waittime 300<c/> flags 0x1a<c/> owning task 0x00000000050EFB88. Continuing to wait.
05/07/2013 10:36:18,spid119,Unknown,Timeout occurred while waiting for latch: class 'ACCESS_METHODS_DATASET_PARENT'<c/> id 0000000431DA63E8<c/> type 4<c/> Task 0x00000000D13DEE08 : 22<c/> waittime 300<c/> flags 0x1a<c/> owning task 0x00000000050E5DC8. Continuing to wait.
05/07/2013 10:34:08,spid157,Unknown,Failed to run resource governor classifier user-defined function. See previous errors in SQL Server error log from session ID 157 for details. Classifier elapsed time: 21 ms.
05/07/2013 10:34:08,spid157,Unknown,Ошибка: 10982<c/> серьезность: 16<c/> состояние: 1.


вероятно ресурс говернер используется

use master
go
-- Get the stored metadata.
select 
object_schema_name(classifier_function_id) as 'Classifier UDF schema in metadata', 
object_name(classifier_function_id) as 'Classifier UDF name in metadata'
from 
sys.resource_governor_configuration
go
-- Get the in-memory configuration.
select 
object_schema_name(classifier_function_id) as 'Active classifier UDF schema', 
object_name(classifier_function_id) as 'Active classifier UDF name'
from 
sys.dm_resource_governor_configuration
go


результат
NULL NULL
в двух запросах
7 май 13, 17:22    [14269429]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
komrad
Member

Откуда:
Сообщений: 5759
sereban,

что вернет ?
только, плз, покажите в читабельном виде (таблица, картинка или fix)

SELECT TOP 25
    os.wait_type,
    SUM(os.wait_time_ms) OVER (PARTITION BY os.wait_type) as sum_wait_time_ms,
    CAST(
        100.* SUM(os.wait_time_ms) OVER (PARTITION BY os.wait_type)
        / (1. * SUM(os.wait_time_ms) OVER () )
        AS NUMERIC(10,1)) as pct_wait_time,
    SUM(os.waiting_tasks_count) OVER (PARTITION BY os.wait_type) AS sum_waiting_tasks,
    CASE WHEN  SUM(os.waiting_tasks_count) OVER (PARTITION BY os.wait_type) > 0
    THEN
        CAST(
            SUM(os.wait_time_ms) OVER (PARTITION BY os.wait_type)
                / (1. * SUM(os.waiting_tasks_count) OVER (PARTITION BY os.wait_type))
            AS NUMERIC(10,1))
    ELSE 0 END AS avg_wait_time_ms,
    CURRENT_TIMESTAMP as sample_time
FROM sys.dm_os_wait_stats os
ORDER BY sum_wait_time_ms DESC;
GO
7 май 13, 17:24    [14269440]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
sereban
Member

Откуда:
Сообщений: 38
komrad,

результат во вложении

К сообщению приложен файл (komrad.csv - 1Kb) cкачать
7 май 13, 17:28    [14269454]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
pkarklin
Member

Откуда: Москва (Муром)
Сообщений: 74930
автор
Возникла проблема из ниоткуда: с какого-то момента пару месяцев назад


Виртуалочка, значит... Трясите сисадминов, что они делали пару месяцев назад.
7 май 13, 17:37    [14269504]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
komrad
Member

Откуда:
Сообщений: 5759
sereban,

ожидание CXPACKET на втором месте
попробуйте следующее

exec sp_configure 'max degree of parallelism',1
reconfigure with override 
go


это отключит использование параллелизма на уровне сервера
не понравится - вернёте обратно на 0 (или на 8)
рестарта сиквела не требует

exec sp_configure 'max degree of parallelism',0
reconfigure with override 
go


статья микрософт
7 май 13, 17:41    [14269528]     Ответить | Цитировать Сообщить модератору
 Re: SQL Server 2008 r2 ужасно тупит после перезапуска  [new]
pkarklin
Member

Откуда: Москва (Муром)
Сообщений: 74930
И вот это очень не нравится:

автор
05/07/2013 10:23:40,Server,Unknown,Cannot use Large Page Extensions: lock memory privilege was not granted.


Выполняйте требования для включения опции Lock Pages in Memory и включайте ее. Нужен рестар инстанса.
7 май 13, 18:07    [14269701]     Ответить | Цитировать Сообщить модератору
Топик располагается на нескольких страницах: [1] 2 3   вперед  Ctrl      все
Все форумы / Microsoft SQL Server Ответить