I want to prevent a login ID from doing Select

I want to disallow a login id from doing a 'Select' on
Table A. but can't.
What I did is Create a Login ID : User
Next, I access Table A's pemission and turn on red cross
under Select Column for the User row
Then log on to Quey Analyzer and do a select . I'm able
to do it( I expect to see permission denied message)
I couldn't even get it... Can someone advise ?
ThnksA user does not have any permissions on a database object unless they have
been granted permissions. Permissions can be granted directly to a users
but it better to grant permissions only to roles. This way, you can more
easily control security with user role membership.
The red X in Enterprise Manager is an explicit DENY. DENY is meaningful
only if the user was granted permissions (usually via some other role
membership) and you don't want a user/role to have this permission.
Usually, one only GRANTs permissions; DENY is used only in special cases.
The only way a user can access an object after an explicit DENY (as you have
apparently done) is if they are a member of a privileged database or server
role. Check to see if the user is a member of the sysadmin server role or
db_owner database role.
Hope this helps.
Dan Guzman
SQL Server MVP
"Jen" <anonymous@.discussions.microsoft.com> wrote in message
news:dc1001c40b34$4f09be20$a501280a@.phx.gbl...
> I want to disallow a login id from doing a 'Select' on
> Table A. but can't.
> What I did is Create a Login ID : User
> Next, I access Table A's pemission and turn on red cross
> under Select Column for the User row
> Then log on to Quey Analyzer and do a select . I'm able
> to do it( I expect to see permission denied message)
> I couldn't even get it... Can someone advise ?
> Thnks

I upgraded from MSDE to 2005 Express, now my apps get 'login faile

All of my RDO (2.0) connections are getting this error:
Login failed for user 'my_user'
All of my apps that use ADO are working fine.
I know the userid/password are correct because I use the same ones with my
ADO apps. Does anyone have any ideas?
Thanks in advance!
apf
Nevermind! The root of my problem was - passwords are case sensitive in
2005! If anyone knows how to turn this "option" off, I would appreciate it.
|||It can't be turned off. It was part of improving password strength to
improve security of SQL logins.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"apf" <apf@.discussions.microsoft.com> wrote in message
news:2786F0F5-CBDB-4B3A-AAC4-67AADE6A4CF0@.microsoft.com...
> Nevermind! The root of my problem was - passwords are case sensitive in
> 2005! If anyone knows how to turn this "option" off, I would appreciate
> it.
>

I upgraded from MSDE to 2005 Express - now my apps get login faile

All of my RDO (2.0) connections are getting this error:
Login failed for user 'my_user'
All of my apps that use ADO are working fine.
I know the userid/password are correct because I use the same ones with my
ADO apps. Does anyone have any ideas?
Thanks in advance!
apfSorry for posting in the wrong forum!
The answer, by the way, is passwords are case sensitive in SQL Server 2005.

I upgraded from MSDE to 2005 Express - now my apps get login faile

All of my RDO (2.0) connections are getting this error:
Login failed for user 'my_user'
All of my apps that use ADO are working fine.
I know the userid/password are correct because I use the same ones with my
ADO apps. Does anyone have any ideas?
Thanks in advance!
apf
Sorry for posting in the wrong forum!
The answer, by the way, is passwords are case sensitive in SQL Server 2005.

I upgraded from MSDE to 2005 Express - now my apps get login faile

All of my RDO (2.0) connections are getting this error:
Login failed for user 'my_user'
All of my apps that use ADO are working fine.
I know the userid/password are correct because I use the same ones with my
ADO apps. Does anyone have any ideas?
Thanks in advance!
apfSorry for posting in the wrong forum!
The answer, by the way, is passwords are case sensitive in SQL Server 2005.