I have to meet the requirement to log on a database all the requests made by my application to an external WCF service. I was suggested to create a kind of a "log table" on my application's support database, isolated from all the other tables, where the logs of this activity could go. However, I wonder if this is really a good practice, i.e., to keep an isolated "logging" table on a database which is supposed to be relational. What would you recommend in this case?
Asked
Active
Viewed 177 times
1
-
1I don't understand why you think a log table is somehow anti-relational. – Joe White Sep 06 '11 at 22:21
-
Just because of the fact it is not connected to any other table, but nothing else. – DotNetStudent Sep 06 '11 at 22:23
1 Answers
4
Why not? After all relational databases operate on matematical set theory which is not relational at all, it is just that when the standards were designed we added a special type that represents a foreign key.
Special types were also made to make it easier and more efficient to store dates, but that doesn't mean a database is designed badly if a table has no rowes with dates in them.
If your log statements genuently don't have any relations, then the database table in which they are stored shouldn't have either.
tomjen
- 3,779
- 3
- 29
- 35