There's no way to do this. You *can* of course monitor which db someone logs into with a client claiming to be SQL*Developer from a workstation claiming to be X in ways already described. I bet that isn't what you want though. I expect you want assurance about access to appropriate systems in appropriate ways. That's a different problem. On Apr 5, 2013 3:46 PM, "Jeff Smith" <jeff.d.smith@xxxxxxxxxx> wrote: > The same way you'd do so with any program? > > Logon trigger that queries module name and insert required info into a > table is generally what I see our customers doing. > > My question would be...why? > > I'll be in Cleveland in May for the Great Lakes Oracle User Group > Conference if you're around and want to swap ideas. > > Jeff > > On 4/5/2013 10:37 AM, Jeffrey Beckstrom wrote: > > Anybody know of a way to monitor who and when someone connects to a > database with Oracle SQL Developer? > > > > > > Jeffrey Beckstrom > > Database Administrator > > Greater Cleveland Regional Transit Authority > > Information Systems > > 1240 W. 6th Street > > Cleveland, Ohio 44113 > > > > -- > > //www.freelists.org/webpage/oracle-l > > > > > > -- > //www.freelists.org/webpage/oracle-l > > > -- //www.freelists.org/webpage/oracle-l