Databases
StackOverflow2013
Postsdbo
POSQL Server Case Sensitivity in Foreign Key
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSQL Server Case Sensitivity in Foreign Key
    primarykey
    data
    text
    <p>We're having issues trying to update all of our user to lowercase usernames in SQL Server. We're doing this to support recent changes in our app. Specifically the following query is failing with an FK Constraint error on another table that references [User].[Username]</p> <pre><code>Update [User] Set [Username] = 'someuser' where [username] = 'SomeUser' </code></pre> <p>The user 'someuser' does exist in the foreign table already and the casing matches 'SomeUser'. The FK isn't set to Cascade on Update at the moment. I was going to go that route, but there are quite a few references to the [User].[Username] column and when I started going down that road it was a bit messy. Besides, I'd rather tackle the root cause - why is SQL enforcing the case match on the Key?</p> <p>I'm not the best with the internals of SQL Server, but I have cheched the COLLATION using the guidance of another SO question (http://stackoverflow.com/questions/1411161/sql-server-check-case-sensitivity) and I get these results.</p> <pre><code>SELECT SERVERPROPERTY('COLLATION') =&gt; SQL_Latin1_General_CP1_CI_AS SELECT DATABASEPROPERTYEX('MyDB', 'Collation') SQLCollation; =&gt; SQL_Latin1_General_CP1_CI_AS select table_name, column_name, collation_name from information_schema.columns where table_name = 'User' =&gt; User Username SQL_Latin1_General_CP1_CI_AS select table_name, column_name, collation_name from information_schema.columns where table_name = 'ForeignTable' =&gt; ForeignTable User_Username SQL_Latin1_General_CP1_CI_AS </code></pre> <p>I'm out of ideas on what to check. Hoping someone has a solution out there. I'm happy to check any settings in SQL (though you might have to guide me to where they're at in Management Studio or the Query to run to get them) or provide any additional detail if I'm haven't given enough info.</p> <p><strong>UPDATE: Error as requested</strong></p> <pre><code>Msg 547, Level 16, State 0, Line 4 The UPDATE statement conflicted with the REFERENCE constraint "FK_ForeignTable_User". The conflict occurred in database "MyDB", table "dbo.ForeignTable", column 'User_Username'. The statement has been terminated. </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USWesleyJohnson
    1. USWesleyJohnson
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSQL Server Case Sensitivity in Foreign Key
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat is the *exact* error please?
      singulars
      1. POSQL Server Case Sensitivity in Foreign Key
      1. USgbn
    2. COI updated the main post with the error. It's just a basic FK constraint error as far as I can tell.
      singulars
      1. POSQL Server Case Sensitivity in Foreign Key
      1. USWesleyJohnson
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload