Tnx for answering Steve. I had figured out as much about the MSDB database.

The weird thing is, that this task has executed flawless up until last week. I cannot find...

Allright!

Tnx. I presume this list id updated when a new hotfix is released.

Tnx again.

OK, with the help of some friendly MS experts thru the Internet and an article or 2 on the subject I have constructed what I needed with the EXECUTE AS...

OK, with the help of some friendly MS experts thru the Internet and an article or 2 on the subject I have constructed what I needed.

Tnx all.

OK, with the help of some friendly MS experts thru the Internet and an article or 2 on the subject I have constructed what I needed.

Tnx all.

Still get truncation errors despite impementing suggestions made here. Not for me.

It might be a great script, but I still have the errors mentioned in the first posting; I thought it was rectified. I cannot find an easy way to remove...

I receive this error:

Msg 213, Level 16, State 7, Line 2

Insert Error: Column name or number of supplied values does not match table definition.

This does not look well...

So I ran this script, and nomatter what parms I use('' or 'sa') I get 1 empty output column named textcolumn. How should I execute this?!

'Have you tried explicitly granting backup admin to the login being used?'

Well no, I have granted SA-rights to the login I use in EXECUTE AS.

What I have found so...

Followed your advise, but no. Let me describe:

I have a SP to execute a RESTORE DATABASE action. This works fine without the WITH EXECUTE AS option. I've created a new...

Tnx for answering; I'll use dynamic sql.

Tnx for answering, Grant.

You're right, I should have mentioned the other reasons myself. I have been monitoring this system for a while now and I see a lot of SQL...

PS,

This is a solution I had tried first.

Don't get me wrong, but have you checked this in SSMS? I don't think so...

BTW, I have found the problem. Some options don't...

I believe you might appreciate this article: