Post reply

How to provide full alter permissions on a db

  • February 11, 2016 at 10:22 am

    #1858094

    Furthermore, BOL states the following for TRUNCATE TABLE

    Books OnlinePermissions

    The minimum permission required is ALTER on table_name. TRUNCATE TABLE permissions default to the table owner, members of the sysadmin fixed server role, and the db_owner and db_ddladmin fixed database roles, and are not transferable. However, you can incorporate the TRUNCATE TABLE statement within a module, such as a stored procedure, and grant appropriate permissions to the module using the EXECUTE AS clause. For more information, see Using EXECUTE AS to Create Custom Permission Sets.

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • February 11, 2016 at 1:28 pm

    #1858160

    SQL!$@w$0ME (2/11/2016)

    User get a warning/error when alter existing table with these rights.

    I've attached the screenshots of the warnings.

    Looking at the error messages/warnings it pointed me to be an application error instead of a genuine SQL error. Searching the internet I found a connect item about it and a technet article. Although Microsoft in the connect item states it is solved, some posters still report the error at later moments.

    So this looks like a bug in SSMS and Visual Studio and you can probably work around it using the actual T-SQL statements. In the connect item it is also mentioned the following additional permissions could prevent the error:

    GRANT view definition on schema:: <schemaname> to <username>

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

  • February 11, 2016 at 2:15 pm

    #1858183

    Great thanks!

  • February 11, 2016 at 4:15 pm

    #1858211

    Heh... keep it simple. Give no one privs to do anything except execute stored procedures. 😀

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • February 11, 2016 at 5:39 pm

    #1858222

    Thanks, this is for developer in a dev box.

Viewing 5 posts - 16 through 19 (of 19 total)

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