manoj2001 (7/28/2009)
So please check in your procedure wherver you are importing data into database.
It's not possible to insert out-of-range values via stored procedures. The SQL query processor will catch that. Data purity errors (which, by the way, these are not) are generally the result of IO corruption or buggy ODBC/OLEDB drivers that do bulk data loads
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability