Skip to main content

Transaction Logs in SQL server. Why we need and how can we read transaction log in SQL Server?

Problem: As we know SQL server Master DB store all the information of table, schema, stored procedures, function, triggers etc. But what is about the operational information, if any problem like error or bug happened in our process execution or some intruder want to do nasty on your server like SQL injection. How can we track this type of issue in Our SQL Server?

Solution: Transaction log may help you to track this problem, Transition log may be the evidence for such type of problems.

Basic Operation captured by Transaction: Before explanation about transaction log, we should to know what SQL operations are captured by transaction log.

Transaction log captured all the DML operation like INSERT, UPDATE, DELETE and also some DDL operation like CREATE, TRUNCATE and DROP,

Why to read SQL Server transaction log?

Transaction log contains all the information about the transaction we performed in our database. If we did some operation by mistake like delete or we lost some data and we want to recover lost data then transaction log may help you to resolve this problem. 

Way of reading SQL Server transaction log.

We can’t read directly to transaction log because of security reason. SQL Server provides us some function to decode it. The function are fn_dblog() and fn_dump_dblog(). For the security purpose transaction log stores the information in encrypted (not human readable) format so we could not read it directly.

View SQL Server transaction log using fn_dblog() funation:

The fn_dblog() is an undocumented function of SQL Server, which is allow to view the transaction log records in the active part of the transaction log file for the current database.

Fn_dblog() function takes two parameters, start LSN and end LSN.

Start LSN: Starting log sequence number, or LSN, you can also specify null which means it will return everything from the start of log.

End LSN: Ending log sequence number, or LSN, you can specify null which means you want to return everything to end of the transaction log.

Note: Undocumented means, if you are using this function in SQL Server, which is against of production database instances executed on your own risk. I will explain only fn_dblog() function only in this article.

How to use fn_dblog() function in SQL Server?

If I will explain uses of fn_dblog() on existing database it may create confusion so I am using new database from creation step by step.

1-Step:  Create database ‘Codefari’.



2-Step: Create table ‘Blogs’.

USE [Codefari]
            ID INT IDENTITY(1,1) NOT NULL,
            TITLE VARCHAR(MAX)

3-Step: In this step we will check how much process has been used by SQL Server to create database and table.

USE [Codefari]
SELECT COUNT(*) FROM fn_dblog(null,null)

You can see 180 steps taken by SQL Server to complete this process.

4-Step: In this step you can see what data available in log.

USE [Codefari]

[Current LSN],
[Transaction Name], 
[Transaction ID],
[Page ID],
[Parent Transaction ID],
FROM fn_dblog(NULL, NULL)

5-Step: In this step we will perform some DML operation and will track transaction information in Log.

INSERT INTO Codefari.[dbo].[Blogs] VALUES('Transaction log in Codefari')
UPDATE Codefari.[dbo].[Blogs] SET [TITLE]='Transaction log in' WHERE ID=1
DELETE FROM Codefari.[dbo].[Blogs] WHERE ID=1

6-Step: This step will show the transaction which we have performed in 5-step.

USE [Codefari]

[Current LSN],
[Transaction ID],
[Transaction Name],
[Page ID],
[Slot ID],
[Begin Time],
[End Time],
[Number of Locks],
[Lock Information]
FROM sys.fn_dblog(NULL,NULL)
WHERE Operation IN

We can see in above steps how fn_dblog() function shows the captured transaction logs and made the transactions in human readable format.

Above experiment and points give consequences as, fn_dblog() can be used when user want to view SQL transaction log. User can easily check the transaction log to see the activities like page splits or objects being drops etc. 

Popular posts from this blog

What is difference between UNION and UNION ALL in SQL Server

We use UNION and UNION ALL operator to combine multiple results set into one result set.
UNION operator is used to combining multiple results set into one result set but removes any duplicate rows. Basically, UNION is used to performing a DISTINCT operation across all columns in the result set. UNION operator has the extra overhead of removing duplicate rows and sorting result.
UNION ALL operator use to combine multiple results set into one result set but it does not remove any duplicate result. Actually, this does not remove duplicate rows so it is faster than the UNION operator. If you want to combine multiple results and without duplicate records then use UNION otherwise UNION ALL is better.
Following some rules for using UNION/UNION ALL operator
1.The number of the column should be the same in the query's when you want to combine them. 2.The column should be of the same data type. 3.ORDER BY clause can be applied to the overall result set not within each result set.
4.Column name of …

Add day to ISODate in MongoDB

We can use $add operator to add days in ISODate in mongodb, $add is the Arithmetic Aggregation Operator which adds number and date in mongodb.

{ $add: [ <expression1>, <expression2>, ... ] }

Note:  If one of the argument is date $add operator treats to other arguments as milliseconds to add to the date.
Example: Suppose we have a Test collection as below.

{"Title" : "Add day to ISODate in MongoBD","CreatedDate" : ISODate("2016-07-07T08:00:00.000Z")}

Query to add 2 days in CreatedDate

db.Test.aggregate([      { $project: { Title: 1, AddedDate: { $add: [ "$CreatedDate", 2*24*60*60000 ] } } }    ])


{ "_id" : ObjectId("579a1567ac1b3f3732483de0"), "Title" : "Add day to ISODate in MongoBD", "AddedDate" : ISODate("2016-07-09T08:00:00.000Z") }

Note: As mentioned in above note we have to convert days in millisecond because $add operator treat to other arg…

Check if an index exists in SQL Server

Many times we come across the scenario where we need to some code based on whether an index exists or not.
The following query may help you to check an index is exists in a particular table or not. Suppose we have a table like dbo.Table1 and it has index idx_Index and in some scenario, we need to check idx_Index exists or not.

System.index catalog view records for each Clustered and Non-Clustered indexes.  We can execute the following query to find out a particular index exists or not in a particular table

IFEXISTS (   SELECT 1 FROMsys.indexes   WHEREname='idx_Index'ANDobject_id=OBJECT_ID('dbo.Table1') ) BEGIN PRINT'Index is Exists' END