Drill from GL90 to payment information LS9 security

When I have a drill around security issue such as I need to restrict access or give access to a drill I will put a trace on the database and then hit the drill around that I am interested in. The trace should then show you which tables(s) the drill is hitting.

Response from our DBA... Can you give us more information?


This doesn't sound familiar. Maybe with more information it may ring a bell. I assume this is done through Lawson commands. I'm not sure how you'd do this at the DB level.

"I assume this is done through Lawson commands..." No I do not use Lawson commands. I am using the tool called "SQL Server Profiler".

We run SQL Server here. If you are on a Oracle database there is also ways to do a database trace. I googled it and DB2 looks like you can do traces as well. I think most database let you turn on tracing.

Tracing is something you will want to do on a test system preferably with few if any users on it. One of the reasons I trace on a system with no users on the system is I can just quickly setup a trace on everything and not worry about being swamped with unneeded data. You can do tracing on production but a little more care might need to be taken to not affect performance and to capture only what you are interesting in. There probably is some way to turn on tracing at the Lawson layer and capture all the SQL. If you turned on that type of tracing in Lawson I would do that on a test system. I haven't bothered to figure out how to trace at the Lawson layer because the "SQL Server Profiler" is a very easy to use tool.

If you are on Oracle you might try a free tool that Oracle has called Oracle SQL Developer. I haven't used the tracing tool in Oracle SQL Developer so I don't know how easy or difficult it is to use. I think it is called 'Monitoring' in the tool.

If your DBA team is seperate from your Lawson team then it might be easier to figure out how to trace on the Lawson layer. I use the route I do because it takes just a few minutes to figure out what table(s) a drill command is hitting.

Thanks. I have passed your information on to our DBA.

To be a little more precise on how I use SQL Server Profiler.

0. Start SQL Server Profiler.*
1. Go into Lawson and get to a point just before a drill or the part of the drill I am interested in.
2. Turn on the tracing.
3. Click into the drill.
4. Shut down tracing.
5. Look through the trace to find the table(s) the drill hit.

* You can start tracing earlier and see if there are background processing running on the database and such that you will want to filter out. If the database if fairly quite you won't need to filter.