I have created a sql server login for an application group consisting of 5 developers. After i created the user, i tested the connection including the previledges of the account on my machine. It has read and write access to the users, and worked as expcted on my machine. But when i gave the developers the credentials, and when the developer1 tried to connenct the database. he is able to connect but not access the tables through SSMS on his machine. This gets even more wierd, when the same login developer2 and developer 3 used it, they is able to access through the tables and browse through the tables.. and are able to what they were expected to do. I wanted to asssume that the developer1 had some configuration issues on his machine,but he is able to access(browse through the tables in SSMS) all the other databases on the instance without any issue. I am not sure what could have caused this problem? Anyone has encountered this type of issue. we are using SQL Server 2008
asked Jan 03 '11 at 03:43 PM in Default
I have run into something similar to this occassionally. It usually happens when someone already has access to a given machine, possibly the same database, possibly other databases. After you update the permissions on the login you might need that user to log off the server entirely and log back on. I've seen it where if they were logged in, no amount of security changes would affect them.
answered Jan 03 '11 at 07:19 PM
Grant Fritchey ♦♦