This is a discussion on ODBC & IGNORE_DUP_KEY Revisited within the MS SQL ODBC forums, part of the Microsoft SQL Server category; --> I posted this question a while back, and got no response. I am re-posting it in the off chance ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I posted this question a while back, and got no response. I am re-posting it in the off chance that someome will be able to help. Thanks a lot, Tim ------------------------------ Hello, I am having a problem with a data loader application written in perl that accesses a Microsoft SQL Server (SQL 2000). The application interprets and bulk loads data into a table. The problem is that because sometimes the same data files get re-run through the system, we have created a unique index on the table with IGNORE_DUP_KEY so we don't get duplicate rows. This works great, but the bulk insert via ODBC always returns a failing value because there are dupes. This makes it difficult to detect if there are any *real* errors (like the datbase has crashed or run out of space). Does anyone have any suggestions? Thanks! Tim |