So I guess i'm gonna have to hack together a solution along the lines of what rkeith mentioned but without using the external bcp utility or varchars for the fields. Microsoft SQL Server 2005 Compact Edition (SQL Server 2005 Compact Edition) is designed for developers who need light weight, in process relational database solution for their applications that can be developed and deployed on desktop, tablet PC and mobile devices.
The approach of doing a constraint-less insert and then filtering out the violating rows makes more sense in your scenario. The batch containing the violating row will be aborted & you will not be able to detect exactly which row had a problem. for Microsoft SQL Server 2005, use the following links. There is no way for the server to ignore some type of constraints like primary key/nullness/uniqueness etc. You can download the SQL Server Native Client from the Microsoft SQL Server 2012 Feature Pack. A low performance approach in this case could be to just have 1 row batches & on failures assume that the row caused a constraint violation (after verifying with SQLGetDiagRec calls that indeed that was the problem. However, the catch is that once a constraint violation is detected by the server the whole batch is aborted meaning none of the rows in the batch are inserted. I believe you can get detailed error information using SQLGetDiagRec ODBC APIs once you see a failure happen by using the same HDBC that you used for performing the bulk operation. I am sure you guys have accounted for this.ĭo I need to go down the route of creating flat-constraint-less tables to stage my bulk uploads into and then call a stored procedure to make the insert and return the rows that failed ?
However some of the tables I am inserting into have constraints.I need to detect any errors caused and prune the erroneous rows from my result set for application side logging.īcp_done and bcp_batch just return -1 (according to the API) and thats just about all it says about errors and bulk uploading.
SQL SERVER 2005 NATIVE CLIENT DOWNLOAD DRIVER
Both the ODBC driver and the OLEDB provider have been released within the Feature Pack for. I want to go down the native client, program variable binding-bulk upload method. Download SQL Server 2005 Native Client ODBC & OLEDB. I am writing an application that needs to perform bulk uploads. I sent this to the microsoft ODBC native client team :
0 kommentar(er)
