People use SQL EM? My thought is that your EM registration is not using the username you think it is. If it is setup for NT Auth then perhaps someone has removed the builtin admins group and your NT login had always been setup on the SQL Server without admin rights. This way if you are a domain admin you had admin rights in SQL Server via the builtin group. Then it was removed and you still can login but have no rights. I'm sure there are other scenerios in which this could have happend. One other example that comes to mind is if you were a local admin and someone removed you from that group. The domain users may be setup on the SQL Server but surely they would not have admin rights. So the same thing would happen here. You were a server admin previously and now you are not.Please post the SQL QA results of this: SELECT SYSTEM_USER, USERselect name, case when sysadmin = 1 then 'YES' else 'No' end SysAdmin, case when SecurityAdmin = 1 then 'YES' else 'No' end SecurityAdmin, case when ServerAdmin = 1 then 'YES' else 'No' end ServerAdminfrom master..sysloginsWhere Name = system_user
Here is something additional to look at, but I wouldn't post this data:select distinct R.Name, USER_NAME(U.UID) from sysmembers M inner join (select * from sysusers where issqlrole = 1) R on (M.GroupUID = R.UID) inner join (select * from sysusers where issqlrole = 0) U on (M.MemberUID = U.UID)order by 2SELECT PRIVILEGE_TYPE, TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, GranteeFROM INFORMATION_SCHEMA.TABLE_PRIVILEGESOrder by 2SELECT o.name, USER_NAME(grantee) FROM syspermissions p INNER JOIN sysobjects o ON p.id = o.idINNER JOIN sysusers u ON p.grantee = u.uidWHERE o.type = 'P'Order by 2SELECT o.name, USER_NAME(grantee) FROM syspermissions p INNER JOIN sysobjects o ON p.id = o.idINNER JOIN sysusers u ON p.grantee = u.uidWHERE o.type = 'FN'Order by 2
Daniel, MCP, A+SQL Server DBAwww.dallasteam.com