Hi all,

Just to let everyone know, I landed up logging a call with MS about this issue and its been confirmed as a bug with SQL Server 2005 SP3.

MS says...