September 25, 2010 at 7:46 am
Hi guys,
I am designing a new application which Provides my clients with Data.
The data will be provided in two ways:
1) Writing the data into a file and placing it on a specific folder on the server.
2) Enabling a query VIA a Web service.
I would like to write a log table for this application but i am unsure of what are the needs of a log table, in other words, what do you guys think are the business requirements of an application log?
How should a log table/tables be designed?
I really don't wake up next year with a business demand I don't have the data for, nor with an extremely big and unused log table..
What are you thoughts, please share!
September 28, 2010 at 7:57 am
y.loewidt (9/25/2010)
I would like to write a log table for this application but i am unsure of what are the needs of a log table, in other words, what do you guys think are the business requirements of an application log?
question is... to log what? 😀 I would say you have to answer this question.
Next question would be... what would be the use of such a log? would it be used to gauge costumer activity? would it be used to charge a fee to your constumer?
As a rule of thumbs, if neither you nor your business side client can think of a valid reason to have a log, you do not need one.
Hope this helps.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply