Rerun failed queries from transaction log backup files

Question

I recently ran into an issue where live production data was failing to insert into my database. When my windows service inserted data the query failed and returned an error message indicating that the transaction didn't succeed.
After restarting SQL the insert statements started working again as they had before. However, because of this I missed about 24 hrs worth of important production data. My server is currently configured to make database backups every 24 hours and make transaction
log backups every hour.
Is it possible to reapply the SQL queries that failed from the transaction log backups? I understand the transaction log backups contain information about what in the database changed, but does it contain the statements that attempted to run but failed?
thanks for any help!

Answer 1

Thanks for all the replies. Here's the error message I'm getting..
An error occurred in
the Microsoft .NET Framework while trying to load assembly id 1. The server may
be running out of resources, or the assembly may not be trusted with
PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check
documentation to see how to solve the assembly trust issues. For more
information about this error: System.IO.FileNotFoundException: Could not load
file or assembly 'microsoft.sqlserver.types, Version=11.0.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot
find the file specified. System.IO.FileNotFoundException: at
System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String
codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint,
StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean
throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName
assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly,
StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean
throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString,
Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr
pPrivHostBinder, Boolean forIntrospection) at
System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence
assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at
System.Reflection.Assembly.Load(String assemblyString)
Basically SQL was having difficulty reading the microsoft.sqlserver.types.dll assembly. This assembly is used for interacting with the Geography data type. I was getting this error message directly from within SSMS - not just in my .net app. Also, there's
not triggers on this table or any custom SQL besides my insert statement.
Then consensus I'm getting is that this isn't really possible to do using transaction logs without extreme difficultly. I installed the ApexSQL before posting on this forum but I wasn't able to find my insert statements.