Reading SQL Server 2008 transaction logs
Logs are proprietary and those solutions are expensive because it is not simple and the average person does not know how to do it. Since you're using SQL Server 2008, have you considered some other more accessible options, such as:


SQL Audit
Server-side trace
Change Tracking
Change Data Capture
Taking snapshots of the DMV sys.dm_db_index_usage_stats
Forcing access through a stored procedure and employing custom logging


I wrote about some of these here (before 2008 was released):


https://sqlblog.org/2008/05/06/when-was-my-database-table-last-accessed