So the other day I answered a question on the Dynamics GP forum about activity tracking in Dynamics GP. The person wanted to know if there was a method to track who looked at a certain window inside of Dynamics GP. The answer was simple… Setup database auditing on the tables in question. The entire exchange can be found here. But over the course of the weekend I was curious to know if you setup an audit on a table say RM00101, I know the audit would tell me if I ran a select statement against it but what would happen if I created a view and included some of the columns in that table would my audit catch that? I honestly don’t know the answer and as a DBA I’m a little disappointed I don’t know.
So I think this would make for an excellent blog series on setting up auditing for Dynamics GP. In my next post I’ll guide you through the creation of the audits. Then we will move onto creating the views and checking our log to find out the answer to the question above.
So I couldn’t wait to find out the answer to my question. It took me about 15 minutes to create the audit and the views to test my audit. The ultimate answer to my question is yes the audit will capture select statements ran against a table when the originating query is ran against a view. I think with the ease of setting this up I’ll be able to post the entire process in a single write up.