Dumps

  • My advice - check the dump.  Chances are it was not a specific query that caused the dump but something else.  Could be a driver issue, could be hardware failure, could be a random computer hiccup and might not ever happen again.

    But until you investigate the dump and/or logs, there isn't a lot anyone can do to help you.

    My guess is it isn't that particular query, but something related to what that query was doing.  Like if the query was an UPDATE and you have a bad sector on the disk, the write may have caused an error on the disk.  I would expect this to take SQL offline as the database would no longer be in a valid state, but I don't know all the voodoo that goes on under the hood of the SQL Engine.

    Or it could be something at the OS level that blocked a read/write such as an antivirus tool and it caused the dump.

    the TL;DR version of my reply - check the logs and check the dump.  Nobody on this forum has access to your system, your logs or your dumps so we cannot tell you what went wrong or why.  Only you have access to that information.  you may be able to send the dump off to Microsoft and get support from them, but without sending a copy of the dump and logs to someone to look at, it is hard to diagnose and debug.

    The above is all just my opinion on what you should do. 
    As with all advice you find on a random internet forum - you shouldn't blindly follow it.  Always test on a test server to see if there is negative side effects before making changes to live!
    I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

  • I ran into a latch timeout issue and followed this instruction and went through the steps and got below stack. It is slightly different. Any advise?

    https://mssqlwiki.com/2012/09/07/latch-timeout-and-sql-server-latch/

    Call Site

    00 KERNELBASE!RaiseException

    01 sqlservr!CDmpDump::Dump

    02 sqllang!SQLDumperLibraryInvoke

    03 sqllang!SQLLangDumperLibraryInvoke

    04 sqllang!CImageHelper::DoMiniDump

    05 sqllang!stackTrace

    06 sqlmin!LatchBase::DumpOnTimeoutIfNeeded

    07 sqlmin!LatchBase::PrintWarning

    08 sqlmin!LatchBase::Suspend

    09 sqlmin!BUF::AcquireLatch

    0a sqlmin!BPool::Get

    0b sqlmin!IndexPageManager::GetPageWithKey

    0c sqlmin!GetRowForKeyValue

    0d sqlmin!IndexDataSetSession::GetRowByKeyValue

    0e sqlmin!IndexDataSetSession::FetchRowByKeyValueInternal

    0f sqlmin!RowsetNewSS::FetchRowByKeyValue

    10 sqlmin!CValFetchByKey::ManipData

    11 sqltses!CEsExec::GeneralEval4

    12 sqlmin!CQScanRangeNew::GetRow

    13 sqlmin!CQScanProfileNew::GetRowImp<0>

    14 sqlmin!CQScanTopNew::GetRow

    15 sqlmin!CQScanProfileNew::GetRowImp<0>

    16 sqlmin!CQScanProjectNew::GetRow

    17 sqlmin!CQScanProfileNew::GetRowImp<0>

    18 sqlmin!CQScanUpdateNew::GetRow

    19 sqlmin!CQScanProfileNew::GetRowImp<0>

    1a sqlmin!CQueryScan::GetRow

    1b sqllang!CXStmtQuery::ErsqExecuteQuery

    1c sqllang!CXStmtDML::XretDMLExecute

    1d sqllang!CXStmtDML::XretExecute

    1e sqllang!CMsqlExecContext::ExecuteStmts<1,0>

    1f sqllang!CMsqlExecContext::FExecute

    20 sqllang!CSQLSource::Execute

    21 sqllang!ExecuteSql

    22 sqllang!CSpecProc::ExecuteSpecial

    23 sqllang!CSpecProc::Execute

    24 sqllang!process_request

    25 sqllang!process_commands_internal

    26 sqllang!process_messages

    27 sqldk!SOS_Task::Param::Execute

    28 sqldk!SOS_Scheduler::RunTask

    29 sqldk!SOS_Scheduler::ProcessTasks

    2a sqldk!SchedulerManager::WorkerEntryPoint

    2b sqldk!SystemThread::RunWorker

    2c sqldk!SystemThreadDispatcher::ProcessWorker

    2d sqldk!SchedulerManager::ThreadEntryPoint

    2e kernel32!BaseThreadInitThunk

    2f ntdll!RtlUserThreadStart

Viewing 2 posts - 16 through 16 (of 16 total)

You must be logged in to reply to this topic. Login to reply