Pablo Campanini-336244 (8/16/2012)
YES......You are absolutely right, I am using SQL Server 2008, not SQL Server 2008 R2, and the bug is killing me!!!!!!.
I will ask my boss to upgrade to R2.
Great reasearch!!!!
Thanks you guys......:-)
You're welcome.
Not sure what you meant by "upgrade" but for the record the SMO bug (if that is what we're in fact dealing with) is a client-side component issue so fixing this will not require a server upgrade. You can use SSMS 2008 R2 against your existing instance. If you install SQL Server 2008 R2 Express with Tools (SQLEXPRWT_x86_ENU.exe or SQLEXPRWT_x64_ENU.exe) you'll get a copy of SSMS 2008 R2 which should resolve your issue without upgrading the server.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato