Recently, a developer at my office rebuilt our data warehouse on new hardware and with a better file/disk layout. We migrated all the data from our old data warehouse to the new and it is now our production environment.The user that built the server had their permissions scaled back so that they were no longer a sysadmin and only had read only access granted. However, this user has discovered inadvertently that they can still make changes to the database. I've found when looking a their user mappings, they are connecting to these databases as dbo. When I look at dbo on the affected databases, the User Type is Windows User, the User Name is dbo, and the login name is the developers AD account. This user does not exist under the database Users and should only have access through the db_datareader role. At the server level, this user is only assigned to the Public server role.I'm obviously missing something but I dont know what it is. It seems odd to me that the dbo user in the affected databases shows this user as it's login. My research on this has not led me to any solutions so I'm hoping someone here can offer insight on how I can set this user to no longer login as dbo on the databases.
↧