Thank you for your question.
We do not yet log extra activity for audit trailing. This can be implemented though in numerous ways. I'd suggest you the following though:
Every content item can be created/removed/updated/deleted via it's content manager class. Every content manager class has Executing and Executed events. You can subscribe for these events on application start for example (in global.asax file) and store all information they provide in separate tables. When there is an operation on a content item, both methods provide command argument showing the content item ID and the operation that has been performed on it.
Adding SQL triggers would be complex I think due to the number of relations that we maintain.
Let me know if you need any additional information, or if you hit a roadblock.
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items