There's another reason you don't want case-sensitivity turned on for the whole
server... the Merant database drivers have a bug in them: they have internal calls to
a stored procedure named sp_SeRvEr_InFo when the actual stored procedure is named
sp_server_info. With case sensitivity turned on every SQL query will infrequently
crash with an error about not finding sp_SeRvEr_InFo.
If you *do* need all comparisons to be case-sensitive, make sure you make a copy of
that stored procedure under the crazy capitalization.
At 07:54 AM 1/24/01 -0500, [EMAIL PROTECTED] wrote:
>Nick, this was helpful, thanks - I didn't realize it was an installation
>option, and I've never seen it installed except with the default setting. I
>looked it up in BOL and it gives pretty good details. I'm sure I've been
>lazy enough with object names, etc. that I wouldn't want case-sensitivity
>ON - half my queries or code might fail. Well maybe not half, but some.
>
>I had been trying out some code with tests of exact (case-sensitive) words,
>such as "WHERE Password LIKE '[S][e][c][R][e][t]', but so far it seems
>that the case-sensitivity setting relates to this too. As a result, SEcret,
>seCRET, SeCrEt, etc. all come up as LIKE the above expression.
>
>So it might be better to say that SQL Server is case-insensitive by
>default, period.
>
>
>Mark
>[EMAIL PROTECTED]
>
>
>
>Sebastian
>
>Apologies, not a very helpful answer.
>
>What I meant was SQL Server is case-sensitive, period.
>
>But actually that's not always true, only if SQL Server is
>installed with a case sensitive sort order.
>
>http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/sql/8_ar_da_
>
>10.htm
>
>Nick
>
>
>
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
