Re: database login vs. operating system login function

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Olivia (anonymous_at_discussions.microsoft.com)
Date: 02/16/04


Date: Mon, 16 Feb 2004 15:11:53 -0800

No, Actually I understand about the application roles but
unfortunately that is not how my environment is set up. We
only use 1 user to connect the db with the application
therefore if I use the db user the user_name() to find out
who is using the application I will always going to find
one user only. So, the only way around is to get the
operating system user if it possible. I was able to
accomplish this in oracle with the following:

select SYS_CONTEXT('USERENV','OS_USER'), sysdate
  into v_user, d_time
  from dual;
 

>-----Original Message-----
>Not sure if I understand your question really well, but
are you looking for
>something similar to Application roles, which allow the
application to
>handle the user authentication? Please refer to SQL
Server Books Online for
>details on Application roles & its usage.
>
>--
>- Anith
>( Please reply to newsgroups only )
>
>
>.
>



Relevant Pages

  • Re: Data File Used Space
    ... Lookup the usage and details of the system procedure sp_spaceused in SQL ... Server Books Online. ...
    (microsoft.public.sqlserver.programming)
  • Re: curious problem in production
    ... > propagated back to the web service. ... > trying to insert into the same sql server database. ... > if it fails in calling the production environment. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: curious problem in production
    ... > propagated back to the web service. ... > trying to insert into the same sql server database. ... > if it fails in calling the production environment. ...
    (microsoft.public.sqlserver.server)
  • Re: curious problem in production
    ... > propagated back to the web service. ... > trying to insert into the same sql server database. ... > if it fails in calling the production environment. ...
    (microsoft.public.sqlserver.programming)
  • Re: curious problem in production
    ... > propagated back to the web service. ... > trying to insert into the same sql server database. ... > if it fails in calling the production environment. ...
    (microsoft.public.dotnet.framework.adonet)