Solved

EXECTE AS Permissions problem while trunacating table

Posted on 2009-05-19
2
204 Views
Last Modified: 2012-05-07
I have a stored procedure, called from Access as a pass through query, that works for me but not for the users. The error message is:

'Cannot find the object "AgrRelations_Materials" because it does not exist or you do not have permissions.'

This procedure truncates then recreates some lookup tables. After a bit of Googling I have come to the conclusion that the problem is due to the TRUNCATE statements which, apparently, do not follow the normal pattern of ownership chaining (which I had never heard of until today). I have kind of confirmed this by replacing the TRUNCATE statements with delete statements, and the users can now use the procedure.

However, I wanted to use TRUNCATE as it is faster, so I tried wrapping an EXECUTE AS then REVERT around the TRUNCATE statements:

EXECUTE AS USER = 'dbo'
TRUNCATE TABLE Relations.AgrRelations_Materials
REVERT

Although this still works for me the users get the following:
Cannot execute as the database principal because principal dbo does not exist, this type of principal cannot be impersonated, or you do not have the permission.

dbo is a user in this database and owns most of the schemas, including the Relations schema that these tables are in.
More Googling and I am stuck. The database has not been restored and does not meet the criteria in kb/913423.

Any help gratefully received: Im a relative newbie and  I expect this will come up a lot.
0
Comment
Question by:Blim2
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 26

Accepted Solution

by:
tigin44 earned 250 total points
ID: 24420378
0
 

Author Comment

by:Blim2
ID: 24420442
The solution recommended is to create a table truncating procedure with EXECUTE AS SELF. I could then call this from my original procedure and maybe even parameterise it to accept table names. That sounds great but  what happens if I leave the company. Won't EXECUTE AS SELF stamp my credentials on the procedure and won't the procedure therefore stop working if my Windows logon is removed?
0

Featured Post

Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article I will describe the Copy Database Wizard method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed
Via a live example, show how to shrink a transaction log file down to a reasonable size.

732 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question