Tag Info

New answers tagged

3

It depends on the SQL SECURITY characteristic you defined when you created the procedure. SQL SECURITY for a stored procedure can be either DEFINER or INVOKER. If your user can not create table but the definer of the stored procedure can, then your user will be able to create a table through the stored procedure. By default, the SQL SECURITY characteristic ...


0

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. You can obviously fine tune ...


0

The problem has something to do with permissions on the underlying server and not SSIS or the MSDB. We had the same problem. Temporarily adding the user's AD account to the local administrators group fixed this for us. Adding their AD account to PowerUsers or Users did not; however, I am certain that we could have found what was missing in the Local Security ...


1

I think you need to clear up the distinction between logins (security entities at the server level) and users (security entities at the database level, which may be associated with a server-level login). What you want to do here is grant CREATE ANY DATABASE to the server-level login. For example: CREATE LOGIN foo WITH PASSWORD = N'bar', CHECK_POLICY = OFF; ...


0

NOTE: When I wrote the answer (below), I did not notice that your question is a MySQL question. Please understand that my answer is for the MS SQL Server platform. I have never used MySQL (and probably never will) so I'm not sure it the permissions model is the same. None-the-less, my "solution" would work in MySQL as long as MySQL provides functions to ...


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: ...



Top 50 recent answers are included