Can any body tell me how can I restrict a user who has Sa previlages, from droping a table. He should be able to do everything except droping the table.
I would like to know if there is any way to restrict users from creating temp tables.
Problem: I am facing problems with lots of temporary objects getting created in my database. The users have read-only access to the database for adhoc-querying purpose through QA. Yet they are able to create temporary tables in tempdb database taking lot of resources on tempdb disk causing abnormally high growth of tempdb.
I create a new user who will have a read only permission on TestDB.
I want to give only select permission on TestDB and also I don't want that the new user will not see any other database.
DENY VIEW ANY DATABASE to user_readonly
ALTER AUTHORIZATION ON DATABASE :: TestDB TO user_readonly
but when I am using the above query then the new user is the owner of the testdb. i don't want that. I want that the user will have only select permission on the table.is there any way?
I would like to disable a user account from logging to the database. I would like to know the difference between deny connect to sql permission and disabling an account by alter login disable. Please advice. Thanks
Just encountered something that I wasn't expected, in that a user who has an explicit deny on a column in a table was able to select it when referenced through a view in a schema they have the SELECT permission on. This seems to me to go against the principle that DENY overrides everything when it comes to permissions? Is this how it's meant to work?
Code is below:-
--create test user CREATE USER TestDenyOnViewUser WITHOUT LOGIN GO
--create test schema (authorization dbo - same owner as dbo schema so ownership chaining will apply) CREATE SCHEMA TestDenyOnView AUTHORIZATION dbo
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,
I have a database X where user A has db_datareader role. User A can select data but cannot update/insert/delete.
Recently user A connected to my database using Brio SQRW tool and could successfully run an update command in database X. As I researched I found out that SQRW uses RPC calls with extended procedures sp_prepare and sp_execute to run an update command.
User A does not have explicit permission to either of these stored procedures. Additionally User A does not have access to master database where there procedures reside.
How do I grant execute permissions on system stored procedures or an extended stored procedure in the master database to a regular user in a different database? Do I need to create the user in the master db also for the permission to given.
I have a custom made database role that has permissions to execute a stored procedure. The store procedure then selects data from some tables. But the role does not have select permissions on the tables. Do I have to allow select on the tables, or can I do this another way?
My development environment is IIS 5.1, asp.net 2.0, Visual Web Developer 05 Express, MS Sql 2005 Express with XP Pro. I used a "stored procedure" in a webpage Formview to insert a record in a child table after inserting a record in the parent table. All went well when testing in VWD. After deploying to remote site on same machine, I get an error "EXECUTE permission denied on object 'usp_Insertdataset', database 'Job_Tracker_SQL', schema 'dbo'"
when trying to insert. I know that SQL Express is not suppose to support stored procedures. Is there a work around? I need to host this site on this machine for the immediate future.
i have a table "employee" , i have given grant all rights to a user in sql 6.5 server . still whenever he tries to access the table from VB he gets an error "execute permission denied on table employee, owner dbo" . if i log in the server with this user name and his password i am able to interact with the table . please help.
i have an application in vb6.0 and sql 6.5 . the sa has created a table as "employee" . there are no stored procedures in the databases. whenever i try to acces the table "employee" , but not as sa ,but as a user defined in the database . i get an error "execute permission denied on object employee, owner dbo " . if i allow users to login as dbo then security is a problem . please help . i know that eexcute permissions are only there for stored procedures , then how this error is coming for the table.
Iam giving permisions to the users to execute procedure which reads and writes the data into the table. And the users cannot directly update the tables.
It works if stored procedure code doesnot have dynamic SQL but gives permision problems when the code contains dynamic SQL .
One limitation of ownership chains is the exec() call. While normal statements in procedures will work with ownership chains, the following one won't
alter proc lsp_deleteorders @OrderID int as begin declare @Sql varchar(200) set @SQL = 'update orders set active = 0 where OrderID = ' + convert(varchar, @OrderID) exec(@SQL) end
we've got a Windows Server 2003 environment with SQL Server 2000 Sp 3.
A stored procedure selects specific data from a user-table which depend on the user executing it. The users are granted execute permission on the stored procedure. But execution fails, if the user is not granted select permission on the user-table, too.
The problem is, that the user must not have the permission on all data in the user-table but on the data concerning him.
In earlier versions of SQL Server and Windows the execute permission has granted sufficient rights to select from the underlying tables. How can this be re-established?
Which fixed database role allows a user to execute a user defined stored procedure while minimizing the amount of permissions given. I think db_Datareader will do the trick.
When I create the chart from the query it works fine but when I convert the same query to the procedure I get the following error. I have proper execute permission of the users.
PLEASE HELP...........
Server Error in '/' Application.
EXECUTE permission denied on object 'mscrm_procname, database 'Servername', schema 'dbo'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Is there a way to grant a group of users the ability to execute some jobs on a server, but restrict their access to others.
We'd like to grant our developers the permission to execute their jobs (many developers and we'd like to avoid a shared account) without giving them the ability to execute our backup, reindex, etc jobs.
Is there a way to grant execute on some jobs, but not all to a Windows group?
We're using the new msdb SQLAgent role to allow them to see all jobs and view output, but there doesn't seem to be a way to grant execute on specific jobs only.
First attempt at using SQL Express developing web app. All works fine within VS2005 dev web server. However, after compiling and creating IIS7 site on same machine without changing connectionString="Server=xxxxSQLEXPVISTA;Database=ABCtest;Integrated Security=true" (SQLVISTA is named instance of SQL Express) The only easy way I can avoid the 'EXECTUTE permissions denied....' is to give the NT AUTHORITYNETWORK SERVICE db_owner role membership. Should I worry? Or should I go through the objects individually and specify permissions? Eventually, this will be on public web server. In advance, thanks. ASM
I add DB to my apllication using the ASPNET membershipBut I got this ErrorEXECUTE permission denied on object 'aspnet_CheckSchemaVersion', Here is the problem page:http://www.tslaw.co.il/default.aspx any Idea how can I fix this problem.Thanks
Environment: Visual Studio .NET 2003 on pc (Windows XP Pro) in workgroup A, ASP .NET application on server (Server 2000 w/ IIS 5 in workgroup A), SQL Server 2000 on same server (Enterprise Edition)..........all on Intranet with static IP's for all machines.
I have the {servername}VSDevelopers group with sysadmin priveleges on SQL Server. I have the {servername}ASPNet user with public on SQL Server.
I can create stored procedures in database ABC on SQL Server from Visual Studio on pc(default named to dbo.{stored_procedure_name}).
I can edit same stored procedures in database ABC on SQL Server from Visual Studio.
I get EXECUTE error when trying to run stored procedure via ASP.NET application on server.
I check, and permissions to objects on SQL Server for VSDeveloper group shows as no permissions.
I set the permissions for all user created objects (tables, stored procedures) to "full" for VSDevelopers.
I'm trying to get a stored procedure working for a website on my local machine that uses ASP.NET 1.1 and MSDE. (I have a single instance of the latter installed, using Windows Authentication mode.)
I've been able to run SQL queries and such directly (using SqlCommand and so forth) by adding the proper reader role to the account MACHINENAMEASPNET. (Substituting my actual machine name for MACHINENAME, of course.) However, when I try to run a stored procedure from an .aspx page, I get the following error:
I've researched this problem here and other places, and every time I get to a response that says to grant execute permission (via OSQL -E) with the following statements:
use mydbasename go grant execute on MySPName to MACHINENAMEASPNET go
(There are sometimes some other intervening statements to add ASPNET as a user account, but when I use those I'm told that the account already exists ... I had added it previously via the Web Data Administrator in order to get reader permissions for SELECT statements and so forth.)
My problem is that the GRANT EXECUTE statement always fails with the following error:
Line 1: Incorrect syntax near ''
Using a forward slash instead doesn't make any difference. If I put single quotes around 'MACHINENAMEASPNET', then the error changes to:
Line 1: Incorrect syntax near 'MACHINENAMEASPNET'
And if I eliminate the machine name, then the error is:
Msg 4604, Level 16, State 1, Server MACHINENAME, Line 1 There is no such user or group 'ASPNET'
So can someone please let me know what I am missing that doesn't allow the GRANT EXECUTE to work?
Here is the stack trace (note that I have altered some names and paths for purposes of security):
Hi I am currently using SQL server 2005 express edition for a website I have created using Asp.Net 2. For this website I call stored procedures that I have created in the databse to return any page data. However, I keep getting error messages say that the login does not have execute permission for the stored procedure. In Sql Server 2005 there does not seem to be an easy way to grant permissions to a stored procedure as you add them. I say this because when I used Sql Server 2000 I would just add the stored procedure, rigth click on it and grant permission to the user. Now this does not seem to be the case with the new version of sql server and I was just wondering whether there is now a new, easy way of doing this. If anyone can point me in the right direction on this... I have managed to get this working by going into the properties of the users atached to the database, adding a list of stored procedures to the "scalables" area and individually ticking the execute checkboxs. However, when I return to add a new stored procedure, the list has disapeared. Is this a bug with Sql server 2005? Thanking you in advance
Suddenly a stored procedure, very much like several others, is givingEXECUTE permission denied on object 'Add_Adjustment', database'InStab', owner 'zhoskin'.server:Msg 229, Level 14, State 5, Procedure Add_Adjustment, Line 18.I'm zhoskin. I am the dbo and created the procedure, and when I lookat its properties, I have EXEC permission. Line 18 is just the returnstatement. The values are all appropriate for the table. So what isusually going on when a stored procedure denies access to its owner?Thanks//Zeke HoskinCREATE Procedure Add_Adjustment (@AdjAcc Int, @AdjType Char, @AdjAmtMoney, @AdjYrMth Int, @AdjDate Datetime)/* Add a Dep Adj (Type Z, Negative) or WD Adj (type Y, Positive) */ASIF @AdjType = 'Z'BEGINInsert Into tblTxn(TxnAcc, TxnType, TxnAmt, TxnSign, TxnYrMth,TxnDate)VALUES(@AdjAcc, @AdjType, @AdjAmt, -1, @AdjYrMth, @AdjDate)ENDIF @AdjType = 'Y'BEGINInsert Into tblTxn(TxnAcc, TxnType, TxnAmt, TxnSign, TxnYrMth,TxnDate)VALUES(@AdjAcc, @AdjType, @AdjAmt, 1, @AdjYrMth, @AdjDate)/*this is just to afect line numbers*/END/* set nocount on *//*space holder*/return/*more space*/GO
I'm fairly new to the world of SQL security (primarily a VB developer) and have a couple of questions/issues to resolve: The error I'm getting in my app is "the execute permission was denied on the object 'MySP'...schema 'dbo'". In essence I cannot execute any stored procedures when logged on as a non-admin user (all this was of course fine in my development environment, now I'm hitting the security issues!). My security is set up as follows:
Using Windows Authentication
I have an Active Directory Group "Group1", to which my non-admin user "User1" belongs. In SQL Mgt Studio I created a login for Group1 under Security/Logins I then created a user under MyDatabase/Security/Users, called "MyDbUser1". This uses the login above. All SPs are owned by dboSo what am I missing?
trying to execute an ssis package from the web - classic asp page
I am using windows authentication to login to the web site
which I assume means i am executing the package under that account
That account being administrator
I am using the code below to execute
Dim objWshShell, obj, objStdOut Set objWshShell = Server.CreateObject("Wscript.Shell") set obj = objWshShell.EXEC("cmd /c dtexec /sq single /ser MPDNETWEB")
this runs find on the command line but I cannot get it to run from the web page.I get the following error.
The LoadFromSQLServer method has encountered OLE DB error code 0x80040E09 (EXECUTE permission denied on object 'sp_dts_getpackage', database 'msdb', schema 'dbo'.). The SQL statement that was issued has failed.
I get this error when I try to preview a report that uses a stored procedure. The stored procedure does not exist in the database, but in the directory I run the report from. The stored procedure declares which database to use, and to create the temp table I want. Do I require special permissions on the sql db I am using to be able to create temp tables? Any help would be great, thanks!
