Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jmsimon09
Starting Member
3 Posts |
 Posted - 2013-10-13 : 10:17:20
|
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
Master Smack Fu Yak Hacker
3873 Posts |
Posted - 2013-10-13 : 20:21:57
|
| 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? |
 |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2013-10-16 : 01:48:14
|
| 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 tableJack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
jmsimon09
Starting Member
3 Posts |
Posted - 2013-10-18 : 04:54:54
|
| Msg 4866, Level 16, State 1, Line 1The 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 1The 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 1Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)".--------------------------------------------------------------------------- |
|
|
|
jmsimon09
Starting Member
3 Posts |
Posted - 2013-10-18 : 04:56:15
|
| :thanks: in advanceit is 1.6gb text file. and more than 5 million row |
|
|
|
James K
Master Smack Fu Yak Hacker
3873 Posts |
Posted - 2013-10-18 : 14:02:09
|
| 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. |
|
|
|
|
|
|
|
|
Help! SQL SERVER IMPORTING LARGE TEXT FILE