Performance issues with language specific sorts?

by Michael S. Kaplan, published on 2006/06/07 03:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2006/06/07/620277.aspx


(No, this is not the font post!)

Bryan Murtha asks:

I've read your blog and I was hoping to get out of it, just how do you setup an internationalized SQL Server database. I read all the docs and the International Software book from Microsoft. Ok, use NVarchar and XML, and your good on the storage. Nowhere on the web or MSDN or anywhere, does it cover just how to get across the inevitable performance issues of not being able to implement language specific sorts. Other then use Oracle is there an answer to this problem?

Unfortunately, I have to reject the premise of the question, in particular the piece that talks about the performance issues with language specific sorts, given the info in Handling multilingual data in SQL Server and in particular the post that links to (Making SQL Server index usage a bit more deterministic). There is definitely a way to make sure that the search is indexed for any desired language sort.... :-)

Now note that you will want to stay away from SQL compatibility sorts, as I pointed out yesterday.

 

This post brought to you by (U+09b9, a.k.a. BENGALI LETTER HA)


# Pavanaja U B on 7 Jun 2006 7:35 AM:

Hi Kaplan,

This is a long standing demand: How do I make user defined sorting in MS SQL Server, if at all it is possible?

Regards,
Pavanaja

# Michael S. Kaplan on 7 Jun 2006 12:12 PM:

Hi Pavanaja,

Not really related to this post, is it? :-)

I actually talk about how to extend SQL Server's language support in a series of posts done here previously. In that case the advice shows how to use the more extended support in Windows to expand SQL Server, but obviously you can extend it using a custom scheme, too.....

go to newer or older post, or back to index or month or day