February 8, 2012 at 9:58 pm
Hi SQL Guru's,
I have not encountered this issue before.
I knew this sysindexes has been depreciated in sqlserver 2008 R2. How ever I have not encountered any issue with working this command.
But yesterday When I issued this command one of the live databases it produces sqldump error and the current session has been crashed. However sys.indexes is working like a charm.
I decide not to use sys.sysindexes on live serves. But why does it has to crash?
Anyone encountered this? The amount of error it generated is very huge and looks scary.
Sample of the error.
2012-02-08 03:21:21.61 spid52 Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )
2012-02-08 03:21:21.61 spid52 (c) Microsoft Corporation.
2012-02-08 03:21:21.61 spid52 All rights reserved.
2012-02-08 03:21:21.61 spid52 Server process ID is 6644.
2012-02-08 03:21:21.61 spid52 System Manufacturer: 'HP', System Model: 'ProLiant DL360 G6'.
2012-02-08 03:21:21.61 spid52 Authentication mode is MIXED.
2012-02-08 03:21:21.61 spid52 Logging SQL Server messages in file 'F:\MSSQL10_50.SQLDB01\MSSQL\Log\ERRORLOG'.
2012-02-08 03:21:21.61 spid52 The error log has been reinitialized. See the previous log for older entries.
2012-02-08 08:29:39.15 spid57 Using 'dbghelp.dll' version '4.0.5'
2012-02-08 08:29:39.19 spid57 ***Stack Dump being sent to F:\MSSQL10_50.SQLDB01\MSSQL\LOG\SQLDump0001.txt
2012-02-08 08:29:39.20 spid57 SqlDumpExceptionHandler: Process 57 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2012-02-08 08:29:39.20 spid57 * *******************************************************************************
2012-02-08 08:29:39.20 spid57 *
2012-02-08 08:29:39.20 spid57 * BEGIN STACK DUMP:
2012-02-08 08:29:39.20 spid57 * 02/08/12 08:29:39 spid 57
2012-02-08 08:29:39.20 spid57 *
2012-02-08 08:29:39.20 spid57 *
2012-02-08 08:29:39.20 spid57 * Exception Address = 0000000000E221B2 Module(sqlservr+00000000007921B2)
2012-02-08 08:29:39.20 spid57 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
2012-02-08 08:29:39.20 spid57 * Access Violation occurred reading address 0000000000000000
2012-02-08 08:29:39.21 spid57 * Input Buffer 174 bytes -
2012-02-08 08:29:39.21 spid57 * select * from sys.sysindexes
2012-02-08 08:29:39.21 spid57 *
2012-02-08 08:29:39.21 spid57 *
2012-02-08 08:29:39.21 spid57 *
2012-02-08 08:29:39.21 spid57 * MODULE BASE END SIZE
2012-02-08 08:29:39.21 spid57 * sqlservr 0000000000690000 000000000423DFFF 03bae000
2012-02-08 08:29:39.21 spid57 * ntdll 00000000778B0000 0000000077A5BFFF 001ac000
2012-02-08 08:29:39.21 spid57 * kernel32 0000000077790000 00000000778AEFFF 0011f000
2012-02-08 08:29:39.21 spid57 * KERNELBASE 000007FEFD8E0000 000007FEFD94BFFF 0006c000
2012-02-08 08:29:39.21 spid57 * ADVAPI32 000007FEFFA40000 000007FEFFB1AFFF 000db000
2012-02-08 08:29:39.21 spid57 * msvcrt 000007FEFDF30000 000007FEFDFCEFFF 0009f000
2012-02-08 08:29:39.21 spid57 * sechost 000007FEFDBE0000 000007FEFDBFEFFF 0001f000
2012-02-08 08:29:39.21 spid57 * RPCRT4 000007FEFF540000 000007FEFF66DFFF 0012e000
2012-02-08 08:29:39.21 spid57 * MSVCR80 0000000075510000 00000000755D8FFF 000c9000
2012-02-08 08:29:39.21 spid57 * MSVCP80 0000000075400000 0000000075508FFF 00109000
2012-02-08 08:29:39.21 spid57 * sqlos 0000000073E80000 0000000073E86FFF 00007000
2012-02-08 08:29:39.21 spid57 * Secur32 000007FEFD3E0000 000007FEFD3EAFFF 0000b000
2012-02-08 08:29:39.21 spid57 * SSPICLI 000007FEFD660000 000007FEFD684FFF 00025000
2012-02-08 08:29:39.21 spid57 * pdh 000007FEFA7E0000 000007FEFA82DFFF 0004e000
2012-02-08 08:29:39.21 spid57 * SHLWAPI 000007FEFDC00000 000007FEFDC70FFF 00071000
2012-02-08 08:29:39.21 spid57 * GDI32 000007FEFF4D0000 000007FEFF536FFF 00067000
2012-02-08 08:29:39.21 spid57 * USER32 0000000077690000 0000000077789FFF 000fa000
2012-02-08 08:29:39.21 spid57 * LPK 000007FEFE020000 000007FEFE02DFFF 0000e000
2012-02-08 08:29:39.21 spid57 * USP10 000007FEFF710000 000007FEFF7D9FFF 000ca000
2012-02-08 08:29:39.21 spid57 * USERENV 000007FEFCB40000 000007FEFCB5DFFF 0001e000
2012-02-08 08:29:39.21 spid57 * profapi 000007FEFD810000 000007FEFD81EFFF 0000f000
2012-02-08 08:29:39.21 spid57 * WINMM 000007FEFA560000 000007FEFA59AFFF 0003b000
2012-02-08 08:29:39.21 spid57 * IPHLPAPI 000007FEFBA20000 000007FEFBA46FFF 00027000
2012-02-08 08:29:39.21 spid57 * NSI 000007FEFE6B0000 000007FEFE6B7FFF 00008000
2012-02-08 08:29:39.21 spid57 * WINNSI 000007FEFBA10000 000007FEFBA1AFFF 0000b000
2012-02-08 08:29:39.21 spid57 * opends60 0000000073E70000 0000000073E77FFF 00008000
2012-02-08 08:29:39.21 spid57 * NETAPI32 000007FEFB5A0000 000007FEFB5B5FFF 00016000
2012-02-08 08:29:39.21 spid57 * netutils 000007FEFCCD0000 000007FEFCCDBFFF 0000c000
2012-02-08 08:29:39.21 spid57 * srvcli 000007FEFD320000 000007FEFD342FFF 00023000
2012-02-08 08:29:39.21 spid57 * wkscli 000007FEFB580000 000007FEFB594FFF 00015000
2012-02-08 08:29:39.21 spid57 * LOGONCLI 000007FEFCE90000 000007FEFCEBFFFF 00030000
2012-02-08 08:29:39.21 spid57 * SAMCLI 000007FEFACD0000 000007FEFACE3FFF 00014000
2012-02-08 08:29:39.21 spid57 * BatchParser 00000000735F0000 000000007361CFFF 0002d000
2012-02-08 08:29:39.21 spid57 * IMM32 000007FEFF450000 000007FEFF47DFFF 0002e000
2012-02-08 08:29:39.21 spid57 * MSCTF 000007FEFDE00000 000007FEFDF08FFF 00109000
2012-02-08 08:29:39.21 spid57 * psapi 0000000077A80000 0000000077A86FFF 00007000
2012-02-08 08:29:39.21 spid57 * instapi10 0000000074BE0000 0000000074BECFFF 0000d000
2012-02-08 08:29:39.21 spid57 * CLUSAPI 000007FEF98E0000 000007FEF992FFFF 00050000
2012-02-08 08:29:39.21 spid57 * cryptdll 000007FEFD3C0000 000007FEFD3D3FFF 00014000
2012-02-08 08:29:39.21 spid57 * RESUTILS 000007FEF98C0000 000007FEF98D8FFF 00019000
2012-02-08 08:29:39.21 spid57 * cscapi 000007FEF97A0000 000007FEF97AEFFF 0000f000
2012-02-08 08:29:39.21 spid57 * sqlevn70 0000000071690000 0000000071890FFF 00201000
2012-02-08 08:29:39.21 spid57 * CRYPTSP 000007FEFD0A0000 000007FEFD0B6FFF 00017000
2012-02-08 08:29:39.21 spid57 * rsaenh 000007FEFCDA0000 000007FEFCDE6FFF 00047000
2012-02-08 08:29:39.21 spid57 * CRYPTBASE 000007FEFD700000 000007FEFD70EFFF 0000f000
2012-02-08 08:29:39.21 spid57 * BROWCLI 000007FEF9880000 000007FEF9891FFF 00012000
February 9, 2012 at 12:36 am
Part of the explanation can be found in this link.
The above explanation does not suite to our data. But someone somewhere has got this issue. Still hoping someone can answer. As of now DBCC CHECKDB is clean. Backup restore, errorlog everything is fine.
Another explanation found here. This link provides a corrupted table which was not in our case.
http://dba.stackexchange.com/questions/11241/sql-server-2008-dbcc-problems
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply