Error loading SQL Server using ODBC connection

shellyburg · Post by **shellyburg** » Thu Mar 01, 2007 3:01 pm

I have a job that sources from a flat file and loads a SQL Server table, straight insert, no transformations, "Clear table then insert rows", Transaction Handling set to 250.

The job was running fine but then the SQL Server table was dropped and recreated with different columns. When I re-imported the table definition and re-linked my source columns, it aborted immediately. One of my coworkers showed me where to set the Quote character from " to 000, which helped the job at least to BEGIN loading records, but it still aborts after a few thousand records are loaded.

The error message merely says "BCIPut call to SQLExecute failed", then just lists the Insert statement and the failed record's data. I was able to manually insert the data from one of the failed records using an insert statement in Query Analyzer. I searched the Forum but could not find anything related to this. Any suggestions?

DSguru2B · Post by **DSguru2B** » Thu Mar 01, 2007 4:52 pm

Welcome Aboard
Do an exact search on "BCIPut call to SQLExecute failed". A lot of such issues have been covered before. Also try resetting the job for additional messages that might help in the diagnosis.

chulett · Post by **chulett** » Thu Mar 01, 2007 4:58 pm

Sounds like you are using an ODBC stage. If all you did was change the Quote character, try pressing the Get SQLInfo button, recompile the job and see if that helps at all.