I was able to get 5.5.1 installed on my new 2008 box. It talks to my database (sql server 2008) if I use the native client for 2008 and the new ms php driver for mssql, but the character encoding seems off.
Have you had any problems with multibyte support with the new Microsoft driver for PHP? I just finished an install on server 2008 with mssql 2008. If I install the native client for 2008 I can talk to the database, but if I use the native client for 2005 (which sugar reccommends) then it doesn't work. Anyway, if I try to save some Kanji (Japanese) characters on a test lead, they end up as ???? in the db.
The problem may be twofold. Some of the fields in the database are "text" instead of ntext or nvchar(max). These fields will have issues with Japanese and other double byte charaters regardless of the driver used. However, the nvchar fields should handle it ok. If I enter in some text like: いちがつ into the SQL Server Management Console, then the nvarchar fields handle it fine and even populate to the webpage fine, but the second I update these fields, the data is corrupted in the DB (which leads me to think it's a driver issue).
If I perform the same test of a text field (e.g. lead source description) then the data is always corrupted (management console or web).
I'm curious, is there an installer that will run an mssql ddl install with nvarchar(max) fields instead of "text" or are they assuming we'll do that manually? Also, does the new mssql driver for php handle multi byte characters or do we have to hack together a FreeTDS install?