Post reply

execute permissions

  • October 29, 2007 at 9:15 am

    #73786

    When I restore a database copy of production to Development, I used to give data reader or writer permissions to the users and that used to set evry thing. I never used to take care of execute permissions on stored procs.

    But at one time execute permissions were not transferred. Is there anything that I am missing here.

    Do I need to give execute permissions explicitly every time when I restore a database copy?

  • October 29, 2007 at 1:37 pm

    #746378

    A restore normally restores permissions also.

    Are you restoring to a single-user mode (restricted) or multiuser?

    I had problems with permissions not being restored in restricted mode (only dbo permissions remained).

  • October 29, 2007 at 3:33 pm

    #746415

    Because you are going to a different server, have you thought about remapping users to logins in the new server?

  • November 2, 2007 at 12:16 am

    #747628

    Check for orphan users and resolve if any. Also you need to give execute permissions if they are not given.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • November 2, 2007 at 8:05 am

    #747752

    Hi,

    After you restore the database from one server(Production) to another(Development), on the development server, under the restored database, run the query:

    sp_change_users_login 'report'

    This gives the list of orphaned entries. Map these orphaned entries using:

    sp_change_users_login 'update_one','login name','user name'

    Renuka__

    [font="Verdana"]Renuka__[/font]

  • November 2, 2007 at 8:15 am

    #747759

    you need to sys-admin rights/permissions to do this job

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply