Case comparison in ntext columns
CrispinH
Posts: 57
I'm using 5.3 comparing, amongst other things, ntext columns where case of the content (as opposed to the column name) is an important issue.
I had a go with ticking the 'Force binary collation' project configuration option (after reading another post in this forum), but that didn't work.
Does 5.3 support case sensitivity in ntext columns?
Regards
Crispin
I had a go with ticking the 'Force binary collation' project configuration option (after reading another post in this forum), but that didn't work.
Does 5.3 support case sensitivity in ntext columns?
Regards
Crispin
Comments
Please refer to http://www.red-gate.com/MessageBoard/vi ... php?t=3775 for a workaround.
Let me know if this doesn't work for you.
Best regards,
David Atkinson
Red Gate Software
Product Manager
Redgate Software
Thanks for your reply. I did that and it worked just fine.
I fall into the category of 'reluctant DBA' because I need to know about SQL Server for by web/software development activities. Collation has passed me by thus far - is there any reason why I shouldn't leave the column with a case-sensitive collation rather than reverting it?
Thanks
Crispin
If you would like SQL Server (and SQL Data Compare) to consider this column in a case sensitive manner going forward, then leaving it would seem the right thing to do.
Regards,
David Atkinson
Red Gate Software
Product Manager
Redgate Software
Thanks. I'll leave it case sensitive.
One small point. On the Project Configuration 'Options' tab there's a couple of tick boxes for Mapping Behaviour marked "Ignore case" and "Ignore spaces", etc. The unwary might think that this refers to content rather than the object name. There is plenty of space to put in 'Ignore case in column name'. Ditto the others.
Crispin
I suppose we hoped that it was sufficient to have it under the "Mapping Behavior" heading, as well as having the Description say that it applies to objects (as opposed to data), but I will concede that there appears to be no obvious reason why the option can't simply be called:
Ignore case for object names and
Ignore spaces in object names
I've put this in as a suggestion.
Thanks,
David
Product Manager
Redgate Software