Search Results

GRANT ALTER ON DATABASE:: joneslocker2 TO username Below script will help you to find what permissions are assigned at the database level : SELECT prin. …

I use powershell based Sync-DbaSqlLoginPermission This command syncs SQL login permissions from one server to another including login permissions, roles, database permissions and more. … Or You can use TSQL based Script DB Level Permissions v3 …

I have used it many times and its a life saver especially when you want to transfer database roles and object permissions from one server to another : Credit goes to the original writer : Bradley Morris … --Script to Reverse Engineer SQL Server Object User Permissions --Written By Bradley Morris --In Query Analyzer be sure to go to --Query -> Current Connection Options -> Advanced (Tab) --and set Maximum …

For future readers, if you want to automate this for your entire sql server estate then, I would highly recommend using dbatools - powershell based tool to ease your life working with sql server. For …

You can create a role and then grant / revoke permissions to it. Any user that is a part of the role will inherit the permissions. …

As per BOL, an account with database owner dbo privileges is required. More info here. So, the user who created it, or a member of the db_owner role can open diagrams.

From BOL : Permissions Required to Run Database Engine Tuning Advisor After you install SQL Server, a user who is a member of the sysadmin fixed server role must launch Database Engine Tuning Advisor …

Once you assign permissions to the role, you can just add users to the role. This way you dont have to manage permissions for individual users. The users inherit permissions granted to role. …

Just grant permissions to the role. …

First you have to Create Login with create database permission. Note that the login cannot drop any databases. USE [master] GO CREATE LOGIN [Kin] WITH PASSWORD=N'somePassw0rd', DEFAULT_DATABASE=[ …

Assuming you are using SQL Server 2008 and up, A better way of doing is to create a role in the database and grant that role permissions. … You can add users to the role, so they will inherit the permissions of the role. -- to grant CREATE, ALTER, DROP OBJECTS (tables, procs, functions, views) with ALTER permissions on the schema. …

GRANT SELECT ON SCHEMA::SchemaA TO SomeRole; go If you have many users that are requiring rights to run the stored procedure, its better to create a role and then add users to the role and assign permissions … Check my answer for Setting user permissions for different SQL Server schemas …

The easiest (quick and dirty solution) but risky in terms of security approach would be to mark the database as TRUSTWORTHY using ALTER DATABASE [your_db_name] SET TRUSTWORTHY ON. Remember that marki …

You have to GRANT the user view server state and view definition on availability group.

Below script will help you copy/clone permissions of one user to another: --- To copy permissions of one user/role to another user/role. … to copy the permissions from SET @NewUser = 'userNEW' --The user or role to which to copy the permissions to SELECT 'USE' + SPACE(1) + QUOTENAME(DB_NAME()) AS '--Database Context' SELECT '--Cloning …