SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 New to SQL Server Programming
 Help! SQL SERVER IMPORTING LARGE TEXT FILE
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

jmsimon09
Starting Member

Philippines
3 Posts

Posted - 10/13/2013 :  10:17:20  Show Profile  Reply with Quote
HELP ME PLEASE... IM TRYING TO IMPORTING A LARGE FILE OR FLAT FILE INTO SQL SERVER 2008 THROUGH IMPORT/EXPORT WIZARD BUT IM ALWAYS GETTING ERROR. LIKE NULL IN MY TABLE. LIKE THAT...HELP PLEASE.

jmsimon09

James K
Flowing Fount of Yak Knowledge

3719 Posts

Posted - 10/13/2013 :  20:21:57  Show Profile  Reply with Quote
Post the exact error message. "Null in a table" does not sound like a SQL server error. Are you perhaps trying to inser a null into a non nullable column?
Go to Top of Page

jackv
Flowing Fount of Yak Knowledge

United Kingdom
2067 Posts

Posted - 10/16/2013 :  01:48:14  Show Profile  Visit jackv's Homepage  Reply with Quote
If you have persistent problems in importing directly to target tables , one tactic is to import into a staging table. Create a clean up process in the staging table. Then run a query to import into the target table

Jack Vamvas
--------------------
http://www.sqlserver-dba.com
Go to Top of Page

jmsimon09
Starting Member

Philippines
3 Posts

Posted - 10/18/2013 :  04:54:54  Show Profile  Reply with Quote
Msg 4866, Level 16, State 1, Line 1
The bulk load failed. The column is too long in the data file for row 1, column 34. Verify that the field terminator and row terminator are specified correctly.
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "BULK" for linked server "(null)" reported an error. The provider did not give any information about the error.
Msg 7330, Level 16, State 2, Line 1
Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)".
---------------------------------------------------------------------------
Go to Top of Page

jmsimon09
Starting Member

Philippines
3 Posts

Posted - 10/18/2013 :  04:56:15  Show Profile  Reply with Quote
:thanks: in advance

it is 1.6gb text file. and more than 5 million row
Go to Top of Page

James K
Flowing Fount of Yak Knowledge

3719 Posts

Posted - 10/18/2013 :  14:02:09  Show Profile  Reply with Quote
Usually I have seen this type of thing happen when you specify the incorrect column separator - for example, if the column separator is a pipe symbol, and you specified the column separator as comma.

In your case, since the error is happening on line 1, that makes it a little easier to debug. Copy the first few lines to a test file, try to import that test file and see what it does. If that fails, which I think it will, examine the columns in the source file and compare to make sure that the target table columns match that.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.06 seconds. Powered By: Snitz Forums 2000