Running under Server 2008, SQL Server 2005 SP2 has the option to "Add New Administrator" from the SQL Server 2005 Surface Ara Configuration. This launches the SQL Server 2005 User Provisioning Tool for Vista. You are then able to grant privileges such as Server SysAdmin role etc.
When I do this the privileges are copied across and appear to be saved but when I return to this tool it is clear that they have not been saved. Anybody else experience this or know how to "make it stick" ?
It seems that the tool is simply not verifying that the privileges are already granted, and it's granting the privileges on every run, which is ok with me (you could check the members of the sysadmin server role.)
Related
Had to go from server 2012 as domain server to workstation.
All is working well and the users can access sql databases with sa login.
The server was running a sql script to backup the databases in task manager.
This is not working anymore. When i see the reports file is says:
The server principal "WYNSSERVER\Administrator" is not able to access the database "PW0001SOC" under the current security contex.
What to do, already tried to open the database in Management studio nad when execute the scipt is working when i connected the database under SQL sa login. But here it is running as Administrator.
How to solve this ?
Let me describe whats happening. I have an application which requires SQL Server 2008 Express.
The application requires the AD-User to have sysadmin rights on the SQL Server. Both SQL and application is deployed using SCCM 2012 R2. My Problem is that when the SQL server is deployed it installs using the current user(System) as a sysadmin on the SQL Instance.
My application will not launch unless the Current user is a sysadmin. Is there anyway I can add an AD-group as a sysadmin on the SQL Server? Preferably using a command line (batch script).
IT worked with AD groups, turned out to be the strict password policy inherited by the domain and my user not having a strict password.
SQLSYSADMINACCOUNTS="ad\group"
I use Sql Server 2008 R2 and SSAS.
After install SQL Server 2008 R2 i joind to domain .
And After Login with my domain user i can not restore database in SSAS.
I get an error windows with this message :
database administrator or server administrator permissions are required to execute systemgetlogicalderives.
i add my domain user to security in MSDB but it not work ?!?
when i login with local user it work.
How i can fix it?
You need to connect to the analysis services instance using SQL server management studio (make sure you use the analysis services option on the connection dialog) as a user that already has administrative permissions on the SSAS instance (it should have asked for a user/group when you installed SSAS)
Then once you are connected, right click on the server, select properties, then security. You can then add more users or groups to the server administrator role from here.
I installed SQL Server 2005 Management Studio Express. When I login to the Database server using Windows Authentication.
I am unable to create tables or create databases. How do I grant the permissions for the users logged in as Windows Authentication to be able to create tables / databases?
In the Object Explorer look for the Security Folder at the top level.
Then under logins right click and choose properties of the user in question.
Grant them further access.
Is there a way to grant execute permissions for a role or a user using GUI (not T-SQL)? I'm using SQL Server 2008 SP1.
Yes, there is a way. Use Permissions page of Database Properties window.
Once database properties windows is displayed, follow steps 1-4 and press OK.
Using steps A, B you can verify it is creating exactly the expected GRANT EXECUTE TO command.
Check out Microsoft SQL Server Management Studio.
It is part of the SQL Server Client Tools package but there's also a free version called Microsoft SQL Server Management Studio Express.
Related resources:
How to grant Permissions on a Stored Procedure (SQL Server Management Studio)
Permissions (SQL Server Database Engine)