If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

How do your users access your database? Do they use a web page, a "fat client", SQL tools like Query Analyzer and Enterprise Manager, or something different? Do your users use Windows Authenication or SQL Autherntication? Do all users have their own logins, or do they share a small number or even one login?

-PatP

In theory, theory and practice are identical. In practice, theory and practice are unrelated.

ms sql permision

The user are using enterprise manager to query some data in the master table.

the sql. the user also use sql Authenication. each user have it own login.

Hope this are the information you require.

Originally Posted by Pat Phelan

I need more information in order to help you.

How do your users access your database? Do they use a web page, a "fat client", SQL tools like Query Analyzer and Enterprise Manager, or something different? Do your users use Windows Authenication or SQL Autherntication? Do all users have their own logins, or do they share a small number or even one login?

Grant the permissions required to this role, and add the users to this role. Remember, if the users are members of either the sysadmin server role, the Domain Admins NT group, or the local administrators group on the box, or are members of the db_owner role in the database, this will not work, and you will have to determine how to back them out of these roles.

If the users have either db_owner, db_datawriter, or sysadmin permissions then you still have a challenge. Otherwise just fix their permissions for those tables. SQL Server starts with the assumption that you have no permissions until the administrator or database owner grants you permissions.

-PatP

In theory, theory and practice are identical. In practice, theory and practice are unrelated.

You may not have permission to perform this operations or the object glsetup may no longer exist in the database

On the role i had deny the update and delete.

Originally Posted by Pat Phelan

If the users have either db_owner, db_datawriter, or sysadmin permissions then you still have a challenge. Otherwise just fix their permissions for those tables. SQL Server starts with the assumption that you have no permissions until the administrator or database owner grants you permissions.