#SQL STUDIO MAP LOGIN TO DATABASE HOW TO#
#SQL STUDIO MAP LOGIN TO DATABASE WINDOWS#

Yes, it exists as both a login (at the server level) and a user (at the database level).

I mean at the database level, the database that is causing you grief.Tara Kizer Microsoft MVP for Windows Server System - SQL Server Subscribe to my blog So there isn't any other solution other than doing this very drastic thing?Īre you sure you are looking in the 'users' list for the particular database? I don't mean the 'logins' list at the server level. These databases all use this WINDOWS_GROUP (which everyone in our company is part of), and deleting it would mean having to re-add it to all our stored procedures, etc.

And I, unfortunately, can't delete it without hosing up 6 other databases. Does the user exist in that list? If so, try deleting it and then mapping it.Tara Kizer Microsoft MVP for Windows Server System - SQL Server Subscribe to my blog Go to the database in Management Studio, expand security and then users. That's my problem.Īre you sysadmin on that server? Meaning, do you have permissions to make that change?Tara Kizer Microsoft MVP for Windows Server System - SQL Server Subscribe to my blog Each time I re-check it, it defaults back to 'unchecked'. Unfortunately, since Monday I am no longer able to Map to one of my databases: 'EtsCubeData', but 6 other databases have no issue with this login. In SQL Server Management Studio under Security/Logins I have a WINDOWS_GROUP login called 'WEST-CA191', and when I right click on it and select 'Properties', and then 'User Mapping' there is a list of Databases I can map to by checking the 'Map' checkbox. Any other ideas?Ĭould you detail what 'map' means in your first post regarding ODBC? I don't see any 'map' fields, so I need to understand what you are referring to.Tara Kizer Microsoft MVP for Windows Server System - SQL Server Subscribe to my blog I would ALTER the user to set the Default_Schema, but I have six other DBs that are working fine with this user, and don't want to do anything to mess them up. I did read, however, that if it is not set, it defaults to dbo. The only thing I did notice is that the Default_Schema is set to NULL. I checked to see if the User is orphaned, and it is not. If you've got the SQL client tools installed, then you can check it out in BOL: ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/1554b39f-274b-4ef8-898e-9e246b474333.htmTara Kizer Microsoft MVP for Windows Server System - SQL Server Subscribe to my blog

Do you know of an article or something that I could reference that explains how to do so? Have you run sp_change_users_login in case the account is orphaned?Tara Kizer Microsoft MVP for Windows Server System - SQL Server Subscribe to my blog Have any of you experienced something like before, and if so how did you work around it? I then tried a couple more times, and for some reason SQL Server is not allowing this id to map. And when I went back into the User Mapping page, the 'Map' box was still unchecked. Upon checking the User Mapping page, I found that our master login that uses Windows Authentication was no longer mapped so I re-mapped it. I came into work this morning to find I could no longer log into one of my SQL Server 2005 databases via ODBC. We've got lots of great SQL ServerĮxperts to answer whatever question you can come up with.

#SQL STUDIO MAP LOGIN TO DATABASE WINDOWS#

#SQL STUDIO MAP LOGIN TO DATABASE HOW TO#

Sql studio map login to database