This SQL shows queries with most "logical_writes":
SELECT TOP 100
st.text,
execution_count,
total_elapsed_time,
total_worker_time,
total_logical_reads,
total_logical_writes,
total_physical_reads,
total_clr_time,
creation_time, last_execution_time,
pl.query_plan
FROM sys.dm_exec_query_stats ps with (NOLOCK)
Cross Apply sys.dm_exec_sql_text(ps.sql_handle) st
Cross Apply sys.dm_exec_query_plan(ps.plan_handle) pl
ORDER BY total_logical_writes desc
OPTION (RECOMPILE);
This T-SQL could help to find direction, but it is not really what you asked for, as logical write != write. and logical write != log write.
It could be very very interesting to find more complete answer to your question.
I could not put this as comment so here it is for you. It is not compete answer to your question because your question can either be correctly answered by person working in Microsoft or Paul Randal(I guess). All I can say for all paractical purposes every information is logged.
You can read the contents of log file using undocumented command
select * from fn_dblog(Null,Null)
If you run it you can see lot of information related to database, pages,extents,locks ect. But it would be difficult for you to extract information from it as it requires a level of expertise to decipher the output.
If you read Books Online document SQL Server Transaction Log architecture and Management it says
Many types of operations are recorded in the transaction log. These
operations include:
•The start and end of each transaction.
•Every data modification (insert, update, or delete). This includes
changes by system stored procedures or data definition language (DDL)
statements to any table, including system tables.
•Every extent and page allocation or deallocation.
•Creating or dropping a table or index.
Log records for data modifications record either the logical operation performed or they record the before and after images of the modified data. The before image is a copy of the data before the operation is performed; the after image is a copy of the data after the operation has been performed.
AFAIK there is no information about query which was fired but the changes which query made is written in transaction log. Changes made to page, extents , locks that were taken, resources that were locked.
Best Answer
Yes but it will be the rollback which actually causes the log to become physically full.
As a transaction generates log records, it will also reserve space in the log for any records required required to rollback. With 20MB of log space remaining and a hypothetical transaction that generates 10MB of log records, you would receive the log full error with 10MB still free and the rollback would then consume that 10MB.