March 28, 2008 at 9:35 am
I get similar problem on one of my customers production server if you get any solution please post it 🙂
Adam Pilon
July 10, 2008 at 8:20 am
hay iv got the same problem today and my production server went dead.
any one how to find what event or statment triggered the stack dump?:w00t:
..>>..
MobashA
July 10, 2008 at 9:09 am
any one ones how can i open SQLDump0032.mdmp ??
..>>..
MobashA
July 10, 2008 at 9:12 am
I suggest you contact Microsoft's customer support services. They can help you with stack dumps.
The mdmp is a mini memory dump. If you have the windows debugger, you can open it. However, unless you're very familiar with assembly you are unlikely to get any value out of it.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 10, 2008 at 9:16 am
thats really sucks.
so if i dont want to call microsoft then i would never know what cosed the crash!!
..>>..
MobashA
July 10, 2008 at 9:21 am
You may be able to get some info from the text file that accompanied the dmp. There's usually a section which contained the input buffer, but there are many cases I've seen where that is empty, because the crash occured somewher that didn't have an input buffer
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply