|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
invalid character value on 7000th record(email below). The database was created using the same setup as other dbs, none of which have had this problem. I ran a trace, which showed several Sort Warnings before the process stopped, but no error messages. The process seems to be a complex query for data, which is then loaded into a table. Any suggestions? I am trying to debug a problem with some data conversion (from a dbf file into a SQL table) For some reason we get this once we have loaded our 7000th record. It is not a problem with the record, not always the same one, has something to do with the limit. Not sure why 7000, but always crashes there. I have tried everything on the code side. Is there any setting in SQL that my enforce some limits on data loading or on the store call, maybe something odd with this table? "Underlying DBMS error[Microsoft OLE DB Provider for SQL Server: Invalid character value for cast specification. (.dbo.a109)]" hi,
If you try to move that table using an ETL tool as DTS, inside the pump you can define how many error as maximum you want to pass. Show quote "naomi" wrote: > > Our developers are trying to pinpoint why a function keeps bombing out > (email below). The database was created using the same setup as other > dbs, none of which have had this problem. I ran a trace, which showed > several Sort Warnings before the process stopped, but no error > messages. The process seems to be a complex query for data, which is > then loaded into a table. > > Any suggestions? > > > I am trying to debug a problem with some data conversion (from a dbf > file into a SQL table) For some reason we get this once we have loaded > our 7000th record. It is not a problem with the record, not always the > same one, has something to do with the limit. Not sure why 7000, but > always crashes there. I have tried everything on the code side. > > Is there any setting in SQL that my enforce some limits on data loading > or on the store call, maybe something odd with this table? > > "Underlying DBMS error[Microsoft OLE DB Provider for SQL Server: > Invalid character value for cast specification. (.dbo.a109)]" > > |
|||||||||||||||||||||||