Learn How SQL Server Large Transaction Log Affect Performance

Alessandro Alpi's Blog

Whenever a user adds, delete, or edit any record in the SQL Server all the changes are maintained in the transaction log. In addition, the background process keeps on writing the each and every transaction in the log and to the database. After that, the transaction log is marked as written. There are two types of recovery model i.e. Simple and Full Recovery Model is used by the database in the SQL Server. However, if the database uses full recovery model all the written transaction logs are maintained in the log. Moreover, it becomes mandatory for the user to manage the transaction log file and take backup on the daily basis. In addition, the transaction log files are big enough if the full recovery model is used for the database. Apart from this, the Transaction logs in the SQL server are the always auto-growth and it is also advised not…

View original post 737 more words

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s