Hello,

i have the same problem. The only solution seems to add then securables as described above or to use the following statement: exec sp_helprotect NULL, 'rolename' or exec sp_helprotect NULL, 'username'. I mean, referring to sql server 2000, this ist a step back for sql server 2005. I also have to look in dbs with some hundreds of tables and special rights for roles and users on parts of the tables. The new behaviour is not good for practive, i think. Or is ist really a bug, that the securables, i have added, are gone and must be re-addet again? I cannot imagine after service pack 1...

Especially migration of sql server 2000 to sql server 2005 seems to be pushed in future...