It does appear the bug still exists in 5.0.2. I modified the existing SQLServer2005DialectTestCase file (though I'm not sure the test is necessarily the best approach, it does assert on the issue...). The changes I made last year look to still be legitimate to fix the issue (since it's still against the 2005 dialect, and not much has changes there).