Will SQL Source Control identify a case change?

troyhunt

I just made a number of case only changes (just column names) to a DB under source control and noticed SQL Source Control didn't pick them up (no changes to commit).

Will the tool natively identify changes in case? Is it dependent on the collation of the DB? These names are persisting through to an ORM so the case becomes pretty important at compile time.

chriskelly

This behaviour could be caused by SQL Server itself if the database has been set with a case insensitive collation.

To look at whether this is the case, see this StackOverflow article:
http://stackoverflow.com/questions/1411 ... ensitivity

If it is the case then you will need to change you database to a Case Sensitive collation.

troyhunt

After spending more time looking at this issue in depth, having Chris unsure of a resolution and not getting any other feedback from this post or the equivalent one on Stack Overflow - http://stackoverflow.com/questions/4302779/can-red-gate-sql-source-control-identify-a-case-change - I'm calling this one a bug. I'd love to be proven wrong, but that seems to be the case (sorry about the pun!).

So to specifically answer my question, no, it appears SQL Source Control can't natively version a case-only change. However, there is a workaround involving making the change in the working directory and submitting this back via TortoiseSVN (assuming the VCS is SVN). Th full details are now in "Defeating Red Gate’s SQL Source Control insensitivity" - http://www.troyhunt.com/2010/12/defeating-red-gates-sql-source-control.html

saulcruz

this is still happening, since 2010 , are there any red gate recommended workarounds?

Sergio R

Hi,

Current versions of SQL Source Control will detect case changes according to the Database collation settings, if it's a database with a CI collation it will not detect differences in case sensitivity.

Thank you,