Referential Integrity Equivalence Question

We get a data feed from SQLServer to load into some oracle tables.
On the Oracle side, the FK constraint is failing after the load.

When reviewing the data that was sent, I discovered that:

(parent data value)
PARENT VAL = V48

(child data value)
CHILD VAL = v48

(FK fails because these aren't the same in Oracle)

Someone in my org mentioned that SQLServer is case insensitive and that's
why it happened.

That doesn't seem possible to me (but perhaps it is) because "v" and "V"
aren't the same at the binary level - they have different code values on
the code page.  (Unless the MSWIN Codepage in use on the SQL Server has
them the same?)

Am I mistaken on that?

Thanks
Chris


--
http://www.freelists.org/webpage/oracle-l


Other related posts: