To help with additional details, here is how it should all look so you can say exactly which portion isn't correct. You have a login for the server, and a user for the database for the account you're having trouble with. On the server and database levels, you'll see a public role (server role and database role). The properties of the public server role won't show users, but the properties of the login will show the public database role for all of the databases (it will be checked, and you can't uncheck it). The properties of the public database role will not show any members either, and the properties of the database user will also not show the public role. Because of all of this, I don't believe you removed the user from the public role.
If you want to try to delete and recreate the user, you can first try to go into the database and just delete the database user. This will leave the login, which you can go into the properties of, and, under User Mapping, there should be no database checked. You should be able to check the database now (because the database user has been deleted), and choose whatever roles you need. If this doesn't work, you can also delete the login along with the database user to try and clear everything out. For one last check on the user, you can run this SQL:
use database_name
exec sp_change_users_login 'Report'
This will show you any orphaned users, which could mean there is still an issue with your user. This can usually be fixed with:
use database_name
exec sp_change_users_login 'Auto_Fix', 'username'
To try and wrap this up before it gets any longer, there could be something else altogether causing your connection issue for this user. If none of this works, can you post up the error message you get when logging in?
Method 1: Connect to the SQL server via SQL Server Management Studio, create a login for the manager under the security\logins folder, in the General properties select either Windows or SQL authentication and fill out the fields accordingly, select the Server Roles properties and select the sysadmin checkbox, click OK to close the new login window.
Method 2: Connect to the SQL server via SQL Server Management Studio. Ask the manager to come over and create a login for himself.
Note: Both methods assume you're running at least SQL Server 2005. If you're running SQL server 7 or 2000, let us know.
Best Answer
A dba is not a system role, it's the title of the person who administers your database server (Data Base Administrator). There is no builtin role called "dba" in SQL.
High-level: DBO is the owner of the specific database and as such has the permissions to do anything within that datbase.