Comments on: SQL SERVER – master Database Log File Grew Too Big

By: SQL SERVER – Weekly Series – Memory Lane – #011 « SQL Server Journey with SQL Authority

Sat, 12 Jan 2013 01:31:20 +0000

[...] master Database Log File Grew Too Big [...]

By: Sushmita

Sushmita — Wed, 27 Jun 2012 14:53:32 +0000

Please I need your help.We have two very big Db’s in one instance and other small DB’s.We have a job runnig which takes a full backup every midnight and everyother day the job fails because of disk space issue. Also we have transaction log backup. Now we are thinking to implement differential back.What do you think can it help us?
Thank you.

By: SQL SERVER – A Quick Look at Logging and Ideas around Logging « SQL Server Journey with SQL Authority

Tue, 12 Jun 2012 01:32:35 +0000

[...] master Database Log File Grew Too Big [...]

By: Rupesh Mishra

Rupesh Mishra — Wed, 23 May 2012 12:27:52 +0000

Hi Yogesh,
A simple solution can be changing the recovery model of your DB from full to bulk recovery model. And before doing this, it is highly recommended that you take a backup (Log and if possible full as well). After performing the bulk operation, do take a log and full backup. For better know how of the recovery models, refer the following link
msdn.microsoft.com/en-us/library/ms189275.aspx

By: Thej Kumar K J

Thej Kumar K J — Thu, 15 Sep 2011 02:14:44 +0000

Hi Dave,

I have one doubt over here. if the masterDB in simple recovery model then how the Log will grow even if we created any user table in masterDB?

By: SQL SERVER – Database Worst Practices – New Town and New Job and New Disasters Journey to SQLAuthority

Tue, 12 Jul 2011 01:32:58 +0000

[...] master Database Log File Grew Too Big [...]

By: Yogesh Sati

Yogesh Sati — Wed, 29 Jun 2011 08:25:26 +0000

Hi Pinal

I have been using bulk insert commands to insert data from text files to my DB. As a result of which(as I feel), the log file of my DB grows enormously (In GBs) and I run out of space in my system. To continue with normal operation I use the command
Backup log with no log
and then use DB->Task->Shrink->File to shrink the log file, which reduces the log file size to 1024 KBs in most cases.
As I have come to know through your blogs that this is not a good practice. I would like to know that what other options do we have to :
1. Prevent the log file to such huge sizes in first case;
2. reduce the size in case it has grown.

By: SQL SERVER – Log File Growing for Model Database – model Database Log File Grew Too Big Journey to SQLAuthority

Sat, 19 Mar 2011 01:33:05 +0000

[...] reading my earlier article SQL SERVER – master Database Log File Grew Too Big, I received an email recently from another reader asking why does the log file of model database [...]

By: Alok Chandra Shahi

Alok Chandra Shahi — Fri, 28 Jan 2011 14:52:05 +0000

will i get the information that which query,procedure or something else were executed? if yes can you give me any link or query or method to get that.

By: madhivanan

madhivanan — Fri, 28 Jan 2011 10:44:19 +0000

If the recovery model of the database is not simple, you can get informations from log file with the help file third party tools

By: madhivanan

madhivanan — Fri, 28 Jan 2011 10:42:06 +0000

If the database is corrupted you can take it from a backup file

By: remil chalat

remil chalat — Fri, 28 Jan 2011 07:02:20 +0000

The ldf file logs all the transactions with the corresponding system change number and is therefore important for instance recovery. All the DML in an instance is logged in here.

So I say it wouldnt be a good idea to delete the log.

By: Alok Chandra Shahi

Alok Chandra Shahi — Tue, 25 Jan 2011 18:25:37 +0000

can you give a detail about benefit of taking backup of log or any database. can i get detail of transaction from log file data.if yes how it is possible if not then what is the benefit to take backup of it.

By: Alok Chandra Shahi

Alok Chandra Shahi — Tue, 25 Jan 2011 18:23:54 +0000

hi pinal,

What is the benefit of taking daily or periodic backup of masterdata.

By: Sriram

Sriram — Thu, 13 Jan 2011 18:50:07 +0000

Edit to my last comment, having large number of logon accounts, droping altering and creating them…

By: Sriram

Sriram — Thu, 13 Jan 2011 18:37:57 +0000

good one, accepted we should never create user defined tables in the master db, although we can create a few stored procs and not so big tables if they are being used to perform some audit operation when the sql server/ system starts. And to you question, i having large number of sql server objects, creating and droping large number of objects might increase the master db log file size.

By: Carla

Carla — Mon, 10 Jan 2011 15:47:03 +0000

Reindexing?

By: Ramdas

Ramdas — Mon, 10 Jan 2011 15:27:35 +0000

Very useful tip, there are times where such things like creating user objects (tables) are done on the master database. Needs to be part of best practices – not to create user defined tables in master database.
BTW i have seen cases where UDF’s are created in the master database, is that a good practice.

Ramdas