Re: trace every SQL statement of a specific user

From: <fitzjarrell_at_cox.net>
Date: Thu, 6 Mar 2008 07:04:59 -0800 (PST)
Message-ID: <4280562f-c0f6-49fa-b30d-6ca2eda135b2@b1g2000hsg.googlegroups.com>


On Mar 6, 7:14 am, Inquirer <sdama..._at_gmail.com> wrote:
> > I never said to place the login.sql file in with the binaries.  I said
> > to place the login.sql file in the directory where your user calls the
> > application.
>
> "in a login.sql file located in the same directory from which the
> connecting application runs will enable full tracing on every session
> she initiates from her desktop. "
>
> all the program binaries (client, server exes, dlls) are in one
> directory.
> I placed the login.sql in that very directory. or I still don't
> understand
> something?

She is not in the binaries directory when she initiates the connection. The login.sql needs to be in the directory where SHE calls the executable, not necessarily where the executable resides:

Executables reside here (for example) => c:\myapp\bin User calls executable from here => c:\mydata

The login.sql would then need to be in c:\mydata.

David Fitzjarrell Received on Thu Mar 06 2008 - 09:04:59 CST

Original text of this message