What Is The Meaning of Kanatype Sensitive Ks and Width Sensitive

what is the meaning of Kanatype Sensitive KS and width sensitive

Both have to do with sorting and typically you would not select these two options. Here is a description couresty of Microsoft.

Kanatype Sensitive

Distinguishes between the two types of Japanese kana characters:
Hiragana and Katakana.

If this option is not selected, SQL Server considers Hiragana and
Katakana characters to be equal for sorting purposes

Width Sensitive

Distinguishes between a single-byte character and the same character
when represented as a double-byte character.

If this option is not selected, SQL Server considers the single-byte
and double-byte representation of the same character to be identical
for sorting purposes.

How to make a column case sensitive in sql 2005 or 2008

ALTER TABLE ALTER COLUMN allows to change collation for a single column:

alter table Foo alter column Bar ntext collate Latin1_General_CS_AS 

(collation might be incorrect)

What does 'COLLATE SQL_Latin1_General_CP1_CI_AS' do?

It sets how the database server sorts (compares pieces of text). in this case:

SQL_Latin1_General_CP1_CI_AS

breaks up into interesting parts:

1. latin1 makes the server treat strings using charset latin 1, basically ascii
2. CP1 stands for Code Page 1252
3. CI case insensitive comparisons so 'ABC' would equal 'abc'
4. AS accent sensitive, so 'ü' does not equal 'u'

P.S. For more detailed information be sure to read @solomon-rutzky's answer.

How to sort the Japanese Character in Sql

Looking at Windows Japanese collations rather then your SQL collations (SQL Server supports both), by trial and error, this works

DECLARE @t TABLE (id int, SomeString nvarchar(100));
INSERT @t VALUES
(1, N'賃貸人側連絡先'),
(3, N'解約連絡先'),
(2, N'賃借人側連絡先'),
(4, N'更新連絡先');

select * from @t order by SomeString COLLATE Japanese_Bushu_Kakusu_100_CS_AS_KS desc

Not sure why you need DESC though. Also note Japanese_XJIS_100_CS_AS_KS does not work

How to join 2 fields of same data that are not case sensitive

Some databases support collation functionality where you can change how the comparisons are done. But the more general solution is to use lower() or upper():

SELECT u.email, u.UserName, ud.CustomerName, ud.CustomerAddress
FROM Userid u JOIN
     Userdetails ud
     ON LOWER(ud.Customer) = LOWER(u.Email);

Note: The use of a function in the on clause will generally impede performance. I would recommend that you change the collation on your database so comparisons are case-insensitive. Or change the data so it is all one case:

update userid
    set email = lower(email)
    where email <> lower(email);

SQL Logic to return ONLY uppercase if matches Else it should return the lower case

Assuming that your column currently has a case insensitive collation you can use

SELECT TOP 1 WITH TIES *
FROM   Table1
WHERE  Name = 'William' 
ORDER  BY CASE
            WHEN Name = UPPER('William') COLLATE Latin1_General_CS_AI
              THEN 0
            ELSE 1
          END 

As the collation is case insensitive it will bring back all variants of William. Ones matching "WILLIAM" will be scored 0 and ones matching any other variant as 1 and the TOP 1 WITH TIES retains the group with the lowest score that exists in the results.

How to pass information from one WPF UserControl to another WPF UserControl?

I've just finished a LOB application using WPF where this sort of problem/pattern appeared constantly, so here's how I would have solved your problem:

1) In the DataTemplate where you create each item in the ListBox, along with it's edit button, bind the Button's tag property to the Customer object underlying that list box item.

2) Create a Click event handler for the button, and set the Button's Click event to fire the handler.

3) In the event handler, set the Content property of the UserControl.

4) Set up a DataTemplate in scope of the User Control (perhaps in the resources of it's immediate container) which describes an editor for that single customer.

Another approach that will work is to declare a Customer dependency property on your EditCustomer class, then set that property (perhaps through a XAML Trigger) when the button is clicked.

I hope this isn't too vague. If nothing else, know that the problem you're facing is very solvable in WPF.

Find two consecutive rows

Assuming the rows have sequential IDs, something like this may be what you're looking for:

select top 1 * 
from 
Bills b1
inner join Bills b2 on b1.id = b2.id - 1
where
b1.IsEstimate = 1 and b2.IsEstimate = 1
order by
b1.BillDate desc

---

Related Topics