Hi, We have a problem storing NaN-s in an SQL Server 2005 DB. When a NaN value is supplied for a field in an SQL INSERT statement, the server responds with the following error: The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 3 ("@val"): The supplied value is not a valid instance of data type float. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater than precision. We have been storing NaN-s in the DB under SQL Server 2003 without any problem. Is this behavior intended in 2005, is it a bug, or is it configurable? Any suggestions will be greatly appreciated.