Everyone is down on Cusors and then they turn right around and use sysobjects in their scripts. 

Why not use the views Microsoft provided?

SELECT specific_name FROM information_schema.routines where NOT specific_name like ('dt_%')

I mean if you are going to do it the proper way, then do it all by the book.

Cursors are like toilet plungers: you hope you don't have to use them, but it's nice to know how just in case.

I looked up the bol. What min(name) here do ?

SELECT @procname = min(name)
FROM sysobjects
WHERE xtype='P' and name > @procname and name not like 'dt_%'

Thanks.

If you wanted to avoid usiing extended stored prcedures you could do it like this. It's a bit more understandable than multiple nested select statements that are required for xp_execresultset to work properly...

-- Specify the user account which should be

DECLARE @login VARCHAR(50)

SET @login = 'my_user_id'

Select

      @sql = Coalesce(@sql, '') + 'GRANT EXEC ON [' + [name] + '] TO [' + @login + ']' + Char(13)

FROM sysobjects WHERE xtype = 'P' AND [name] NOT LIKE 'dt_%'

EXEC (@sql)

To grant execute permissions to a user for all stored procs in a schema. Using the GUI

Right click a stored proc.

            Click properties

Click view schema permissions

Add

            Object type -> user -> ok

Brows

            Choose user -> ok

Click on the user

            Under grant check execute.