Tag Info

New answers tagged

0

I know that the post is old, but to make this work be sure that the user you set as Run As in the Job, has access to the proxy and is in the list of the proxy Principals. If the user is systemadmin in sql it will not get saved in the list and you will get the error.


1

Plan A: If dull and shiny don't change, leave both in effect?... GRANT ... TO dbuser@dull ...; GRANT ... TO dbuser@shiny ...; But, beware, this could leave the "production" system accessible to "QA". (Assuming that is really what you are doing.) Plan B: A simple script (after transferring): UPDATE mysql.user SET host = 'shiny' WHERE host = 'dull'; ...


0

This is a known issue with SQL Server 2012. It used to work in previous versions. The Microsoft Connect item can be found here: https://connect.microsoft.com/SQLServer/feedback/details/769502/permissions-not-replicating-for-certain-object-types-when-using-a-sql-server-2012-distributor We first noticed it on the MSDN Forums here: ...


1

To connect to SSMS they need the CONTROL SERVER permission. No, that is not true at all. I hope you didn't learn that from any documentation, blog post or presentation. If you did, you should tell us where, so we can hunt them down and correct it. In order to connect, they need to be a member of the public role (granted by default to all logins). To do ...


1

Since this is a syntax error, first thing to do is to double check the syntax letter by letter. In the MySQL Reference Manual you can find that the correct syntax for GRANT is GRANT ALL ON *.* TO 'someuser'@'somehost'; and that IDENTIFIED BY is used for changing the password. Compared to your command the difference is in priv_level, that sould be ...


0

So basically it sounds like you want to give this group of individuals db_owner access to all databases on the server. The way to do this is: Create a local group account on the Windows Server (e.g. \\MYSERVER\SpecialGroup) Add the AD accounts to that group. Create a SQL Server login for \\MYSERVER\SpecialGroup Then create a job, that runs every night (or ...


1

Well, if you have an existing superuser role called "super1", you could do: CREATE ROLE super2 WITH SUPERUSER LOGIN; GRANT super1 TO super2; And, in theory at least, any of super1's privileges would be transferred over to super2. However, I'm not sure your question makes much sense, since superusers generally are allowed to override any privilege ...


0

Finally I've found the source of those permissions: This AD user had an "orphan" user in database with higher permissions than AD group. So in order to connect to instance this user needs to be a part of the group But after the connection he can get permissions directly from his "orphan" user in DBs Even if the group that he is a part of is only public group ...



Top 50 recent answers are included