Bulk Insert Error with SQL 2000

Bulk Insert Error with SQL 2000

Post by Ken Crai » Wed, 09 Jan 2002 05:18:25

Our New 2000 production server will not see a fixed field as a null.
We import a file in SQL 7.0 That has |    | sometimes and it imports
this as null. Some of our other extracts may have || and it also sees
this as null. SQL 2000 sees || as null but will not see |    | as null.
Is there a setting or something that I need to adjust to fix this issue.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!


1. Error when bulk insert follows another large bulk insert

I am running a job out of MS SQL Enterprise Manager where the first step
turns off transaction logging, the 2nd step is a large bulk insert step,
and the 3rd step is another large bulk insert step.  I receive the
following error when executing the 3rd step.  Is this error occurring
because the database is still comitting data from the previous large bulk
insert at the same time as it is performing the next bulk insert?  If so,
is there a workaround?  Thank you for any help you can provide.

Error message from Step 3 (2nd bulk insert):
Backup, CHECKALLOC, bulk copy, SELECT INTO, and file manipulation
(such as CREATE FILE) operations on a database must be serialized.
Reissue the statement after the current backup, CHECKALLOC, or
file manipulation operation is completed. [SQLSTATE 42000] (Error 3023)  
The statement has been terminated. [SQLSTATE 01000] (Error 3621).  
The step failed.

Posted via CNET Help.com

2. Update Statistics Error:-243 C-ISAM:-103

3. Bulk Insert in SQL 2000 using ODBC or DB-Lib

4. Simple IF statement

5. sql server 2000 memory issues when bulk inserting

6. 6.5 to 2000 SQL conversion

7. Bulk Insert and loop (SQL Server 2000)

8. OpenRoad FAQ

9. Broken BULK INSERT with SQL 2000

10. SQL Server bulk insert error

11. Bulk Delete (as opposed to Bulk Insert)


13. Insert Error: SQL Server 2000