August 1, 2009 at 11:22 am
hey Guys,
I was using import/export wizard to load a flat file with comma delimiter with 2.4 billion records.. seems like data got loaded now sure if full data got loaded BUT this is the error I got..
- Copying to [DBName].[dbo].[TableName] (Error)
Messages
Information 0x402090de: Data Flow Task: The total number of data rows processed for file "N:\fileName.txt" is 2180171755.
(SQL Server Import and Export Wizard)
Information 0x402090df: Data Flow Task: The final commit for the data insertion has started.
(SQL Server Import and Export Wizard)
Error 0xc0202009: Data Flow Task: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Unspecified error".
(SQL Server Import and Export Wizard)
Information 0x402090e0: Data Flow Task: The final commit for the data insertion has ended.
(SQL Server Import and Export Wizard)
Error 0xc0047022: Data Flow Task: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Destination - TableName" (38) failed with error code 0xC0202009. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
(SQL Server Import and Export Wizard)
Error 0xc0047021: Data Flow Task: SSIS Error Code DTS_E_THREADFAILED. Thread "WorkThread0" has exited with error code 0xC0202009. There may be error messages posted before this with more information on why the thread has exited.
(SQL Server Import and Export Wizard)
August 1, 2009 at 11:35 am
Oh topic has sql 2006 instead of sql 2005... typo sorry!
August 1, 2009 at 11:57 am
I think that wizard comes in both x86 which is 32bits and x64 which is 64bits if your source is not x64 you may want to use the x86 instead of the x64.
That takes us to why not split the task to smaller sizes so the task will not fail, if you are not running fancy hardware make your import smaller.
Kind regards,
Gift Peddie
August 1, 2009 at 8:09 pm
seems like table has all the records... still this error. I guess it is due to size issue... I was importing from flat file to sql using wizard.. file size was around 105gb with around 2.4 billion records.
Thanks for your response.
August 1, 2009 at 8:27 pm
I you have 105gig you need at least 20 to 30 smaller sized operations.
Kind regards,
Gift Peddie
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply