|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Today @ 9:03 PM
Points: 31,406,
Visits: 13,723
|
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Wednesday, April 17, 2013 3:39 AM
Points: 1,768,
Visits: 1,312
|
|
I guess; "A user to act like another user"
looks correct answer as per the following MS article:
http://msdn.microsoft.com/en-us/library/ms188304.aspx
--------------------------------------------------- "Thare are only 10 types of people in the world: Those who understand binary, and those who don't."
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 5:02 AM
Points: 2,365,
Visits: 1,825
|
|
According to BOL the answer seems to be the first option.
"Keep Trying"
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 11:51 AM
Points: 5,232,
Visits: 7,023
|
|
Hi Steve,
Impersonation is a generic term for using the security settings of a user that you are not authenticated as. This term is used *both* for
(a) database users impersonating other database users (using the EXECUTE AS command, or executing stored procedures with the EXECUTE AS clause), which requires the aptly named IMPERSONATE permission - see also the link free_mascot posted; and
(b) the SQL Server service connecting to another instance under the context of an authenticated Windows user.
So both the first and the third answer are correct.
Hugo Kornelis, SQL Server MVP Visit my SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Wednesday, December 21, 2011 3:09 PM
Points: 390,
Visits: 86
|
|
Hi Steve,
next time I suggest to have check boxes instead of radio boxes. You show us two correct answers!
Ralf
I feel sorry with all of us - whom was using the first correct answer
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: 2 days ago @ 6:14 AM
Points: 2,379,
Visits: 423
|
|
Could someone explain why the first answer would be incorrect?
I felt it was a correct answer based on SQL 2005 BOL:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/6d156257-8c80-4062-a6a0-acc6797b293f.htm
SQL Server 2005 supports the ability to impersonate another principal either explicitly by using the stand-alone EXECUTE AS statement, or implicitly by using the EXECUTE AS clause on modules. The stand-alone EXECUTE AS statement can be used to impersonate server-level principals, or logins, by using the EXECUTE AS LOGIN statement. The stand-alone EXECUTE AS statement can also be used to impersonate database level principals, or users, by using the EXECUTE AS USER statement.
Implicit impersonations that are performed through the EXECUTE AS clause on modules impersonate the specified user or login at the database or server level. This impersonation depends on whether the module is a database-level module, such as a stored procedure or function, or a server-level module, such as a server-level trigger.
Thanks!
|
|
|
|
|
SSChasing Mays
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 8:19 AM
Points: 642,
Visits: 198
|
|
| I believe there is more than one correct answer to this question... I think this depend on your perception of Impersonation.
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Friday, March 15, 2013 2:43 PM
Points: 3,924,
Visits: 1,554
|
|
I think answer should be option 1 and 3.
-- Impersonating allows a member of the sysadmin fixed server role or db_owner fixed database role to impersonate another user
http://blogs.msdn.com/sqlclr/archive/2006/06/16/635003.aspx
SQL DBA.
|
|
|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Today @ 9:03 PM
Points: 31,406,
Visits: 13,723
|
|
|
|
|
|
SSChasing Mays
      
Group: General Forum Members
Last Login: Monday, February 18, 2013 3:22 PM
Points: 626,
Visits: 835
|
|
|
|
|