for the most part, my (sql server 2005) application prefers to be case
insensitive, so my default database collation is case insensitive. However
there are a few columns which I really want to be case-sensitive. Is there
any significant performance impact to setting some columns to have a
different collation from the database as a whole?
...Mike"Mike Kraley" <mkraley@.community.nospam> wrote in message
news:B7D9FD39-82D5-4256-BCCA-A11CD3A693D8@.microsoft.com...
> for the most part, my (sql server 2005) application prefers to be case
> insensitive, so my default database collation is case insensitive. However
> there are a few columns which I really want to be case-sensitive. Is there
> any significant performance impact to setting some columns to have a
> different collation from the database as a whole?
> --
> ...Mike
No, in fact being case-sensitive would have a minor performance boost.
(Even better would be to use binary collation.)|||Hello Mike,
I agree with MIchael that case-sensitive would have a minor performance
boost though it may improve perofmrance a little. You may want to refer to
the following link for more discussion on this topic
How to perform case sensitive searches in SQL Server?
http://vyaskn.tripod.com/case_sensi..._sql_server.htm
Please feel free to let's know if you have any further comments or
concerns. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
<http://msdn.microsoft.com/subscript...ps/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscript...rt/default.aspx>.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Friday, March 30, 2012
performance implications of collation changes
Labels:
application,
case,
caseinsensitive,
collation,
database,
default,
howeverthere,
implications,
insensitive,
microsoft,
mysql,
oracle,
performance,
prefers,
server,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment