I want to Grant permission for a table which is residing at another server's database. I have added the server as a linked server to my database and i am able to do all DML (Insert, Update, Delete) operations from the source server to the target server's table. But i am not able to Grant permission for the table.
I run the following query...using sql analyzer dbo.aCVChangeSQLPassword 'user1','user1',''I am logged in as user1 in the sql analyzer...It chnages my password, in sql server, however gives me this message...Grantor does not have GRANT permission.Password changed.(1 row(s) affected)Server: Msg 4613, Level 16, State 1, Procedure aCVChangeSQLPassword, Line 27Grantor does not have GRANT permission. Line no 27 has the folliwng code that I execute...
Hi I have installed Sql server 2005. I tried to give "Create database" permission to master database I am getting an errorGrantor does not grant permission (Microsoft SQL Server, Error 4613) May I know what is the reason for this.How to resolve it. RegardsKaran
Hi, I newly created one database (using creat database testdb ). After that i created login name and password for that database ( using create login login1 with password = 'pass1'; use testdb; command) and i created user for that login name ( using create user user1 for login login1 command). Then i connected testdb database using login1. But when i trying to create table in that database, it thrown error. Anyone please tell me that how to assign all privileges to the user user1?
Hi all,Before using SQL Server 2000 Developer Edition I did not get this error message. I had been using the trial edition of SQL Server 2000.I only get it with stored procedures.I solved my problem by giving the ASPNET login "db_owner" privs, which I didn't need to with the trial edition and is not best practice from a security angle.I login under the Windows based admin account. (not using mixed mode).Hope someone can shed some light.Thanks.
I am new to sql server. right now i getting used to management studio.I am trying to creata a new object / a new database but i am getting an error which says permission not granted
I'm trying to run the Bulk Insert statement but in order for me the run it, i need to have the sysadmin permission. Can someone show me how to grant sysadmin permission to my SQL Server user? This is really urgent. Thank you in advance.
Does anyone know how i can grant select permission on more than one table in the same database using a single grant commmand....its painful to use grant statement seperately on each table
On our production SQL 2005 servers I want to give developers readonly access to each user database and also give them the ability to see stored procedures. Readonly is handled through db_datareader, but how do I give them the ability to see stored procedures without granting permission to execute them?
There's something I can't quite figure out about user creating
The application that I'm currently working on is interacting with DB, therefore every time you use application you need to login as user which is fine. The problem is that certain users should be able to create new users and the new user may even have the same level of permissions as the one that's creating it ( like admin creating another admin acount or some like that).
Question is how can I allow users to create these user with giving them as few permissions as possible.
If there's is somewhere a code sample on the net I would appreciate the link.
I have an web application where the users has to run SQL scheduled jobs from the webpage. How to assign permission to a specific user to run specific jobs without making them a member of a Sysadmin role?
Any ideas you all smart people? Thanks in advance!
How to grant DROP table permission within a database to an SQL login. I could see in Databae properties-> permission tab, there is an option to grant CREATE TABLE, EXECUTE permission etc, but not DROP table permission. How to grant it?
The requirements are: 1. the user has read-only permissions to dbo tales. 2. the user can do everything within the rpt schema, which contains all objects analyzing dbo tables. 3. the user does not have any permission outside rpt schema, except permissions in #1.
The current solutions are: 1. grant the user select only on dbo tables. 2. make the user the owner of rpt schema. 3. Grant the user database permission on create table/create procedure/create view/create function.
My question is - in step 3, should I just grant "Alter" database permission to the user? Granting Alter seems to be cleaner and simpler. According to MSDN,
"Alter" confers the ability to change the properties, except ownership, of a particular securable. When granted on a scope, ALTER also bestows the ability to alter, create, or drop any securable that is contained within that scope.
What role or system privilege do I need to grant to a user if he need to read the data from a table which is in a link server object? where I can find the document about these commands.
I have a user who needs access to views like(dbo.viewnameabc1,dbo.viewnameabc2 and so on...) dbo.viewnameabc* and anytime the user creates the view he already have the permission to view those views....
GRANT SELECT ON [dbo].[TblAreaCatmap] TO [admin] prevent grant from being automaticly add to each column?
Is there a way when you issue a grant select to a table or a view to not also grant select for each column.
The problem is when you use the grant command it automaticly adds the grant command to each column. I want to grant the permission at the table level so when the table is scripted it only has a single grant command instead of a grant for the table and a grant for each column which is not needed.
The sql managemnt studion interface will allow you to do this but onlt by using the interface. If you issue the above command from a query window it also creates A GRANT FOR EVERY COLUMN. How can I stop this behavior.
I am writing a stored procedure which updates a table, but when I run the stored procedure using a login that I have granted execute privileges on, then I get a message that I cannot run an update on the table. This would happen in dynamic sql... while my SQL has parameter references, I don't think it is considered dynamic SQL?
sproc: CREATE PROCEDURE [schemaname].[SetUserCulture] @UserID int , @Culture nvarchar(10) AS UPDATE dbo.SecUser SET Culture = @Culture WHERE UserID = @UserID
In SQL Server 2005 SP2 I want to grant the ability to create views to a user but in order to do this it requires that the users has the ability to grant alter on a schema.
Is there any way to grant this privilage without granting alter on schema also?
Have a certificate and symmetric key that i have used the following to GRANT to logins. How can I find out which SQL logins have the GRANT CONTROL and GRANT VIEW DEFINTION?
GRANT VIEW DEFINITION ON SYMMETRIC KEY:: Symetric1 TO Brenda GRANT CONTROL ON CERTIFICATE:: Certificate1 to Brenda
SQL Server 2005, Windows Server 2003: On our production db, the SA acct has been locked. I realize that I could enable mixed mode and then connect via an administrator -- but we are already running in mixed mode, and our BUILTINAdministrators account has sysadmin permissions turned off.
As it stands, the only user I can connect as does not have permission to modify any of the login info.
What recourse do I have at this point? Can I disable mixed-mode and re-enable it (via registry)? If so, will it reset the SA account or rebuild the BUILTINAdministrators login for me?
Or do I need to contact Microsoft, and if so is there anything they can do?
I have my SQL 7.0 server set for Mixed security. I see now (finally)the advantages of having windows authentication security for windowsgroups.I do most of my developing in Access Projects which require a login ofsome type. I have been using my SQL login to develop with SQL andthen when I give it to the user, I set the project to use Windowsauthentication. I want to be able to have Windows authentication onmy domain account but the user name for my windows account is the sameas my SQL account and it won't let me change the existing account.Now what happens is after I develop the product I have to have theuser login and go in and change to windows authentication. It won'tlet me do it with my sql account.I fear that if I delete my sql account and create a windowsauthentication account all the views, sps, etc. that I have createdwill still have the reference to the sql login and therefore not work.Do I need to have a generic sql account for developing? One thought Ihad was to create a new domain account so I can create that windowslogin and at least get my most recent projects working like I want to?Hope this makes sense to someone.Thanks in advance for your time.Sherry
I've got a weird issue on my hands. I've got a 2 node/instance SQL 2005 SP2 Enterprise cluster on Server 2003 Enterprise, that's getting an odd event log error over and over. The service account that runs everything (SQL Services, Agent, Analysis Svcs, etc...) is a domain admin. The account is not locked out. SQL Server seems to be running fine. But, if you look in the SQL Server logs or the application logs, all you see are thousands of errors just like this:
Type: Failure Audit Source: MSSQLSERVER Event ID: 18456 Login failed for user 'domainServiceAccount'. [CLIENT: xxx.xxx.xxx.xxx]
(BTW - the ip addr in the error is of that virtual instance of SQL Server.)
On the Server Evt log, it only shows up in the App log. In the security log, all of the audits related to this service acct are successes.
It happens on both instances of the 2005 cluster. But my SQL 2000 cluster (which uses the same service account) is having no problems at all. I've tried everything I could think of to diagnose/fix the issue and just can't seem to figure it out.
- verify that BUILTINAdministrators is an SA in SQL - verify that NT AUTHORITYSYSTEM is an SA in SQL - verify that the service account is an admin on both physical boxes. - verify that there are no 'deny' permissions set on any of the system databases for the service account (or the two above built in groups).
Any ideas? I can't find anything on the web about it that's helped so far. Basically everything seems to be negated by the fact that the account is NOT locked out and the fact that the account is a domain admin. Luckily it's not causing any problems for me (at the moment), but I'm trying to diagnose a different issue and I can't seem to shake the possibility that both of the issues are related.
I have an application that uses Integrated Windows authentication. My Web.config looks like below <add key="dbconnection" value=" server=XXX;Initial Catalog=XXX;persist security info=False;Integrated Security=SSPI;Pooling=true" /> When users try to access my application, they get the below error: Execute permission denied on object 'SprocName', database 'DBNAME',Owner,'dbo' The Only way I could get rid off the error is if I set DBO permissions for the user group on the databse. Can someone suggest how to set up a security group with the ‘necessary’ permissions on SQL SERVER (ie read,write execute Sproc etc) and not too many extra ones, like DBO. Thanks,
SQL Server 2005 anomoly? In SQL Server Management Studio I granted specific permissions to user "A" to do Select, Insert, Update, Delete on Table "B" - When I logged on as User "A" and attempted the Insert imto table "B" I got the following error: "Insert Permission Denied on Table B, Database C, Schema dbo" Is this a problem with the dbo schema?
Then I went back and created a stored proccedure "D" with the exact same Insert statement inside the procedure. I granted User "A" execute permission on the stored procedure "D". I then logged on as User A and executed Stored Procedure "D". No Problem - stored procedure executed fine with the Insert. I attempted the Insert statement again - straight SQL - as User "A" and got the same error as above ("Insert Permission Denied.....") Strange behavior - cannot do a SQL. Insert even though user has permissions but can execute a store procedure with the same Insert statement. What gives?