Dear all,

How do i grant a user select permissions for ALL possible sets of a
database such as tables, views, stored procedures, assemblies, ...etc.

Is there a way to grant that user all of those permissions in a simple
way?
Ihave been selecting table by table, view by view, ..etc. for a user
using the sql server 2005 management studio and it's frustrating how
long it takes.
I've also checked the msdn for help and found that i can grant a user
permissions for a selected table using sql script, but i hope there is
a way to grant that user those permissions for all tables, views,
....etc. in a simpler way

Best regards

So you want users to have select permissions on all tables and views?
(You can't get select permissions on stored procs, only permissions
like execute)

You can grant a user the db_datareader fixed database role and
according to the sp_dbfixedrolepermission stored procedure this will
allow them SELECT permissions on all database objects (that it makes
sense to have SELECT permissions on, of course).

I am not sure what sort of permissions you want to grant to users on
other database objects on which it doesn't make sense to have a SELECT
permission (e.g. stored procs, functions, assemblies) but if you could
describe this further maybe we can work out what will be suitable and
make the work easier?

Well, all the user tables, user stored procedures, user views, user
assemblies ...etc. in simpel words, all the database objects excluding
the system objects.

1) Users can issue SELECT statements against any user created table or
view. How about INSERT, UPDATE and DELETE statements?

2) Users have EXECUTE permissions any user created stored procedure and
issue the appropriate commands against any user assembly that has been
loaded. I assume users cannot issue ALTER statements (e.g. ALTER
PROCEDURE) or DROP statements

3) Users should not be able to issue DDL commands (e.g. CREATE TABLE)
or modify the schema in any way. They can't create tables, views,
stored procs etc

Unfortunately, I don't think there is any fixed database role that has
the fine grain you are looking for. For example, the db_datareader role
will not give you all you want and the db_owner role will give you too
much.

I believe that the only way for you to get the kind of control you're
after is to manually define the permissions to what you want them to
be.

Sorry I can't be of more help.