Re: Trap SQL statements in network traffic instead of database

From: Sandra Becker <>
Date: Thu, 17 Aug 2017 13:07:19 -0600
Message-ID: <>

Good news. The boss decided to take a few days off. The team lead said to use FGA and be done with it. 30 mintues later, I have the information I need with minimal impact to the database. I have say, I like this feature.

Thanks for all your suggestions.


On Fri, Aug 11, 2017 at 2:43 PM, Sandra Becker <> wrote:

> We need to produce a "log" of sql statements--along with the user, IP (or
> host) they are coming from, and the sql statement--for another team to
> analyze. My manager does not want to user auditing because of the
> uncertainty of the load on this critical database. He suggested doing a
> SPAM port capture. I opened a ticket with our SAs and they wanted to know
> what ports. I gave them the listener ports. The SA ran a tcpdump (said it
> was verbose), but it didn't give any information on users, app servers, or
> sql statements. I really don't know what I'm doing here, just passing
> information between my manager and SAs. So, questions:
> 1. Will tcpdump give me what my manager is asking for? If yes, what are
> the options the SA should use?0
> 2. Is there a better way to retrieve this information without using
> database auditing?
> Any assistance you can provide will be greatly appreciated.
> --
> Sandy B.

Sandy B.

Received on Thu Aug 17 2017 - 21:07:19 CEST

Original text of this message