Hi there Rahul Lohar
SQL Server has no native way to “undo one committed transaction” from the log. The supported path is a point-in-time restore to a time just before the bad DELETE/UPDATE, usually side-by-side to a new database, then copy/merge the corrected rows back into production. If the primary must be restored, take a tail-log backup, then restore full + diff + log backups with STOPAT to the target time. options like fn_dblog/fn_dump_dblog exist but are undocumented/unsupported; third-party log readers (ApexSQL, Redgate, etc.) can reconstruct undo scripts, but they also rely on internal log parsing and come with caveats (TDE/encryption keys needed, not all operations supported
enable temporal tables, CDC, or Change Tracking so you can self-service logical recovery without log spelunking.
If this helps kindly accept the response thanks much.