Friday!!

SBD

CirquedeSQLeil (7/19/2010)

John Rowan (7/19/2010)

I'm in the mid-west. They would make money here. I'll be adding...

I'm in the mid-west. They would make money here. I'll be adding that to my...

Delicacy

Zophobas morio

(not so random worm - my next project is to breed them for pet consumption)

I'm glad you figured it out. I would still suggest that you take steps to make your data types consistent accross your tables.

Here's how I've done it.

1. Create a Data Flow task.

2. Inside Data flow, use OLE DB Source adapter to get your XML. I use a stored procedure. I...

Salvation

--==== Build test table

DECLARE @Table TABLE (

RowID int IDENTITY(1,1) NOT NULL PRIMARY KEY,

DecimalValue decimal(18,2) NOT NULL

)

--==== Insert test data into table

INSERT INTO @Table(DecimalValue)

SELECT 2316842 UNION ALL

SELECT 594649871 UNION ALL

SELECT...

Comparing 123 accross those data types should evaluate to an equality. Are you seeing something different.

On another note, you may want to correct the problem of storing the same...

Nope, it will round the incoming data to fulfill the datatype, but not change the #.

That's because 124757266 is a whole number. If your number was 1247572.66156413, then you'd get 1247572.66.

If you want to add a decimal point, divide it by 100.

INSERT INTO...

Rowdy Roddy Piper

Macho Man