SQL server is crashing when data is importing from a CSV. Crash Dump File.

Question

Post reply

SQL server is crashing when data is importing from a CSV. Crash Dump File.

Duran

SSChampion

Points: 13259
More actions
August 29, 2014 at 1:28 am

#298876

Hello,
I wondered if anyone might be able to point me in the right direction as to wha to look for in Crash dump files. SQL server is crashing when I try to importing 1GB of data into a table. I have the following files available to me...
Event Log (More on that below)
Reprt.wer
.tmp.mdmp
tmp.appcompat
.tmpwerinternal metadata
Obviously the Event log I can open, but its not giving me much info, as for the others, I do not know how to open them to gain an insight into what is going wrong. Nothing is showing up in the SQL logs.
EventID : 19019
MachineName : MachineName
Data : {185, 55, 0, 0...}
Index : 14183
Category : Server
CategoryNumber : 2
EntryType : Error
Message : The MSSQLSERVER service terminated unexpectedly.
Source : MSSQLSERVER
ReplacementStrings : {The MSSQLSERVER service terminated unexpectedly.}
InstanceId : 1073760843
TimeGenerated : 27/08/2014 11:49:17 AM
TimeWritten : 27/08/2014 11:49:17 AM
UserName :
Site :
Container :
EventID : 1000
MachineName : MachineName
Data : {}
Index : 14181
Category : Application Crashing Events
CategoryNumber : 100
EntryType : Error
Message : Faulting application name: sqlservr.exe, version: 2009.100.4276.0, time stamp: 0x5115d467
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000163bc1c40
Faulting process id: 0x72c
Faulting application start time: 0x01cfc0bb7c37fabf
Faulting application path: C:\Program Files\MSSQL2K8R2\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.
exe
Faulting module path: unknown
Report Id: 4e28a4d2-2d8c-11e4-bd3b-005056947247
Source : Application Error
ReplacementStrings : {sqlservr.exe, 2009.100.4276.0, 5115d467, unknown...}
InstanceId : 1000
TimeGenerated : 27/08/2014 11:48:56 AM
TimeWritten : 27/08/2014 11:48:56 AM
UserName :
Site :
Container :
The following line isnt really helping...
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Can anyone be kind enough to give a little advice, please? Any help will be greatly valued. Thank you.
Regards,
D.

Viewing 6 posts - 1 through 6 (of 6 total)

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

Eirikur Eiriksson SSC Guru Points: 182948 More actions · Answer 1

Quick question, are you on SQL Server 2008 (not R2) 32bit?

😎

Duran SSChampion Points: 13259 More actions · Answer 2

Thank you for reading and responding so quickly, Hmm, I'd have to check, but I'm fairly sure it's 2008 r2 64bit, I can confirm and come back Monday. Have you seen this before?

Regards,

D.

Eirikur Eiriksson SSC Guru Points: 182948 More actions · Answer 3

Duran (8/29/2014)
Thank you for reading and responding so quickly, Hmm, I'd have to check, but I'm fairly sure it's 2008 r2 64bit, I can confirm and come back Monday. Have you seen this before?
Regards,
D.

My phone playing tricks on me when reading the message before, you are on 2K8 R2;-)

I've seen same/similar on 2K 32bit about four years back. If I remember correctly I either resolved the issue by using Bulk-Logged or set the Batch Size + Simple Recovery

😎

Jeff Moden SSC Guru Points: 1004638 More actions · Answer 4

What are you using to do the import with? Bulk Insert, BCP, SSIS or ???

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Duran SSChampion Points: 13259 More actions · Answer 5

Hello Jeff and everybody.

To confirm it is SQL 2008 R2 64bit, build 10.50.4276.0

It was SQL server running a bulk insert job, I thought it was direct, but it seems to be getting run through an third party application. I wonder if the application might be the issue rather than SQL Server.

Thank you for your help on this, much appreciated.

Regards,

D.