"MADNESS" <MADNESS@discussions.microsoft.com> wrote in message
news:72E5BA66-7F45-480E-A2F5-336CCD986B65@microsoft.com...
> Hi there, We are currently reviewing upgrading our Transactional
> Replication
> from SQL 2000 to SQL 2005.
>
> Out test environment consists on SQL 2000 Publisher, SQL2005 Distributor,
> SQL 2000 Subscriber, and a SQL 2005 Subscriber across 4 different servers.
> We
> successfully configured a transactional publication and subscription to
> the
> SQL2000 subscriber. However the same publication errors when the snapshot
> is
> being applied to the SQL2005 subscriber as below:
>
> OLE DB provider 'STREAM' for linked server '(null)' returned invalid data
> for column '[!BulkInsert].price'. (Source: MSSQLServer, Error number:
> 7339)
>
> To troubleshoot this we bcp'd out the table manually and tried to insert
> it
> to the subscriber using bcp with the exact same error msg appearing. We
> managed to drill this down to one particular row, and one particular
> column
> which was a float. The value of this float is 2.8128137561472325E-312. We
> then created a table on the SQL2005 server with only float column, and
> tried
> to insert this record, with the resulting msg
>
> Warning: the floating point value '2.8128137561472325E-312' is too small.
> It
> will be interpreted as 0
>
> This appears to be a valid float on SQL2000, so why is it not valid on
> SQL2005. Any suggestion would be most welcome!! This is a nightmare for
> replication!!!
>
>

"Paul Ibison" wrote:

> According to MSDN, the original value should also be too small for SQl
> Server 2000
> (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_fa-fz_6r3g.asp).
> As a matter of interest, can you try BCPing it into a staging table on SQL
> Server 2000 also to confirm that you don't get the same message there.
>
> Cheers,
>
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>