Lugiment Log Explorer

Does any one know all the capabilities of the Lugiment Log
Explorer ? . Here is what our management wants to do:
Get the information on who did what in the database ?.
Here is the better part; Our application uses an 'sql
server account' that is in a 'database role'. Of course we
apply the permissions to the database role but the SQL
Server is accessed from the MTS server and when we look at
the -->Current Activity-->Process Info-->Host column we of
course see the name of the MTS server.
Is Lugiment Log Explorer tool (Or any other tool) capable
of giving us this information alone with the transaction
information ?.
Thanks for any input.Hi
No.
Unless you enforce impersonation, all the way from your application to SQL
Server, no tool can help. Log tools only know about a user as much as
sp_who2 can give you.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Todd" <anonymous@.discussions.microsoft.com> wrote in message
news:48cb01c52106$83a9a260$a401280a@.phx.gbl...
> Does any one know all the capabilities of the Lugiment Log
> Explorer ? . Here is what our management wants to do:
> Get the information on who did what in the database ?.
> Here is the better part; Our application uses an 'sql
> server account' that is in a 'database role'. Of course we
> apply the permissions to the database role but the SQL
> Server is accessed from the MTS server and when we look at
> the -->Current Activity-->Process Info-->Host column we of
> course see the name of the MTS server.
> Is Lugiment Log Explorer tool (Or any other tool) capable
> of giving us this information alone with the transaction
> information ?.
> Thanks for any input.|||> Get the information on who did what in the database ?.
Probably want to check out Entegra, another Lumigent offering. The slogan
is "know who did what to which data when" or something like that.
> Here is the better part; Our application uses an 'sql
> server account' that is in a 'database role'. Of course we
> apply the permissions to the database role but the SQL
> Server is accessed from the MTS server and when we look at
> the -->Current Activity-->Process Info-->Host column we of
> course see the name of the MTS server.
That's right, and since that's all that SQL Server knows, that's all any 3rd
party tool will know as well. You might have to put some additional logging
into the MTS Server or whatever app is using it if you want to capture data
about what statements they're calling.
A