Hi @tobz ,
Any suggestion on how to get it run faster or alternative method for getting the Current LSN
You can also use the DBCC Log() command to see log information which includes Current LSN, but this command will not give you detail information.
As for the slow data query, it may be caused by the excessive amount of your data. Can you query with conditions as mentioned by Ryan?
The query should be optimized, and full table scans should be avoided as much as possible. First, you should consider establishing indexes on the columns involved in where and order by. This is where you should pay attention to improve the query speed when the data is large.
And you can refer to this blog about fn_dump_dblog.
Best regards,
Seeya
If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar queries.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.