RE: Referential Integrity Equivalence Question
- From: "Hariharan, Abhishek" <AHariharan@xxxxxxxxx>
- To: "christopherdtaylor1994@xxxxxxxxx" <christopherdtaylor1994@xxxxxxxxx>
- Date: Fri, 27 Sep 2013 21:41:52 +0000
The SQLServer instance can be case sensitive or insensitive depending on the
collation settings.
See below links on how to change/set
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/f5cd6d91-0a0e-41be-8801-97d5b7bef98b/how-to-make-sql-server-data-case-sensitive
http://msdn.microsoft.com/en-us/library/ms179254.aspx
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Chris Taylor
Sent: Saturday, September 28, 2013 3:01 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: 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
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
