Hello JunChen. Thanks for bringing this to our attention. This problem has been fixed. The correction will be included in a future release for SQL Server. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)