SQLServerCentral / Article Discussions / Article Discussions by Author / Discuss content posted by Patrick Cahill / Execute As / Latest Posts

RE: Execute As

Jeff Moden — Sun, 04 Dec 2011 11:51:58 GMT

[quote][b]califny (11/27/2011)[/b][hr]Hi, I follow the steps on 2008R2. When I execute EXECUTE AS LOGIN = 'ApplicationUser'I got error:Cannot execute as the server principal because the principal "ApplicationUser" does not exist, this type of principal cannot be impersonated, or you do not have permission.Any ideas? Thanks![/quote]Do you have a login called "ApplicationUser"?

RE: Execute As

califny — Sun, 27 Nov 2011 13:59:42 GMT

Hi, I follow the steps on 2008R2. When I execute EXECUTE AS LOGIN = 'ApplicationUser'I got error:Cannot execute as the server principal because the principal "ApplicationUser" does not exist, this type of principal cannot be impersonated, or you do not have permission.Any ideas? Thanks!

RE: Execute As

gholden — Fri, 04 Feb 2011 08:52:49 GMT

Thanks for the article, very helpful on many levels. This is the most straightforward and concise discussion of execute as and encryption that I've encountered. Great article.

RE: Execute As

Jeff Moden — Wed, 02 Feb 2011 23:17:54 GMT

[quote][b]charles evans (2/2/2011)[/b][hr]You're right the one can't declare and assign in the same line with local variables in SQL 2005. Adding that feature in SQL 2008 made turning ad-hoc versions of stored procedures sooo much easier.[/quote]All MS needs to do now is figure out that column and variable selection along with variable assignment in the same SELECT (kind of like they do in update) would be incredibly useful and my day would be made! :-)

RE: Execute As

Jeff Moden — Wed, 02 Feb 2011 23:15:13 GMT

[quote][b]Patrick Cahill (2/2/2011)[/b][hr]This is my first article...[/quote]Then my hat is really off to you, Patrick. Comprehesive code with a decent format embedded in a well written article that explains everything along the way... you just can't ask for much better on your maiden voyage as an author. Well done, again![quote]...and I found out that coming up with a good title is more difficult than it seems.[/quote]Heh... you noticed that? Even a well written fellow like Steve Jones runs into that problem. However, if that's the worst problem with one of your articles, it's not really a problem

RE: Execute As

codebyo — Wed, 02 Feb 2011 18:09:15 GMT

Thank you for your article, Patrick.Not only does it cover the implementation of EXECUTE AS but it also demonstrates a very interesting example of certificates and builtin criptography. Much appreciated contribution. :-)

RE: Execute As

charles evans — Wed, 02 Feb 2011 16:07:52 GMT

You're right the one can't declare and assign in the same line with local variables in SQL 2005. Adding that feature in SQL 2008 made turning ad-hoc versions of stored procedures sooo much easier.

RE: Execute As

BCC-493036 — Wed, 02 Feb 2011 13:37:34 GMT

I think that the following line of code only works on SQL 2008DECLARE @i INT = 10In SQL 2005, it should beDECLARE @i INTSET @i = 10

RE: Execute As

Patrick Cahill — Wed, 02 Feb 2011 08:28:22 GMT

Jeff, thank you for the kind words. This is my first article, and I found out that coming up with a good title is more difficult than it seems.

RE: Execute As

Jeff Moden — Wed, 02 Feb 2011 08:20:50 GMT

I haven't taken the time to run the code yet either... but I did read the article. The title of the article doesn't even come close to describing the great features used in this article. I realize that EXECUTE AS is the main purpose of the article but this article also does a very, very nice job of providing an introduction to one important type of security. I'd call the article something like "Restricting Access Using EXECUTE AS".If the code in this article turns out to be as good as the article itself, I'll be making a permanent link to this one. It's short, sweet, and very much to the point.Well done, Patrick.

RE: Execute As

charles evans — Tue, 01 Feb 2011 22:24:39 GMT

Hello I noticed in the article that you say the test database will be called MyTesting, however the script creates it as TestDB. Just thought I'd point this out. Otherwise, good article from what I can tell without actually running the code.Cheers,Charley

Execute As

Patrick Cahill — Tue, 01 Feb 2011 20:54:24 GMT

Comments posted to this topic are about the item [B]Execute As[/B]