HI
I am new to SSRS reports, and currently on a project with a MNC,
I got a doubt on "Accent Sensitivity" in SSRS while building reports.
Can anyone suggest any hints on it.
I am using SSRS 2008.
Thanks
HI
I am new to SSRS reports, and currently on a project with a MNC,
I got a doubt on "Accent Sensitivity" in SSRS while building reports.
Can anyone suggest any hints on it.
I am using SSRS 2008.
Thanks
HI vikash,
"Accent Sensitivity" is a criteria specified in SSRS reports to treat the data underneath it.
It works similar to case senitivity flag i.e. either to treat the data as case senisitive or not.
In Accent senistivity it will treat the data as for vowels like a and á, o and ó are treated in the same way if it is accent in-sensitive.
Some systems treats 'a' and 'á' differently as the underneath ASCII values are different i.e. 'a' = 97 and 'á' = 225.
--sqltech56
hi sqltech56,
thanks for the prompt reply and the elaborated description.
I have a small doubt in this if "Accent Sensitivity" is for treating the data as per pronunciation. Then what is “Collation” used for.
Hi vikash,
I guess you might have seen this on SSRS while adding custom datasets for your report.
To make you clear, I will describe all the elements in the option section while building dataset in SSRS.
a) Collation: Collation is the assembly of written information into a standard order. These are set of rules that determine how the data is sorted or compared. And the Collation name is a string identifying the alphabet or language whose sorting rules are applied when dictionary sorting is specified.
b) Case Sensitivity: Data in SQL server can differ in meaning based on differing use of uppercase and lowercase letters. This is a flag to determine to follow this rule or not.
c) Accent Sensitivity: This is a criteria specified to treat the data as per its pronunciation. Accents can be confused with dialects which are varieties of language differing in vocabulary, syntax, and morphology, as well as pronunciation. Like a and á, o and ó are treated in the same way if it is accent in-sensitive.
d) Kanatype Sensitivity: This specifies that SQL Server distinguish between the two types of Japanese kana characters: Hiragana and Katakana. This is a flag to use it or not.
e) Width Sensitivity: It shows how SQL Server treats the single-byte characters (half-width) and the double-byte characters (full-width) for the same data. This is a flag to determine whether these two set of data to be treated same or not.
Let me know for any uncertainty.
You must log in to post.