Couple of the days ago, I received following email and I find this email very interesting and I feel like sharing with all of you.
Note: Please read the whole email before providing your suggestions.
“Hi Pinal,
If you can share these details on your blog, it will help many.
We understand the value of the master database and we take its regular back up (everyday midnight). Yesterday we noticed that our master database log file has grown very large. This is very first time that we have encountered such an issue. The master database is in simple recovery mode; so we assumed that it will never grow big; however, we now have a big log file.
We ran the following command
USE [master]
GO
DBCC SHRINKFILE (N'mastlog' , 0, TRUNCATEONLY)
GO
We know this command will break the chains of LSN but as per our understanding; it should not matter as we are in simple recovery model.
Read more: Journey to SQL Authority with Pinal Dave
Note: Please read the whole email before providing your suggestions.
“Hi Pinal,
If you can share these details on your blog, it will help many.
We understand the value of the master database and we take its regular back up (everyday midnight). Yesterday we noticed that our master database log file has grown very large. This is very first time that we have encountered such an issue. The master database is in simple recovery mode; so we assumed that it will never grow big; however, we now have a big log file.
We ran the following command
USE [master]
GO
DBCC SHRINKFILE (N'mastlog' , 0, TRUNCATEONLY)
GO
We know this command will break the chains of LSN but as per our understanding; it should not matter as we are in simple recovery model.
Read more: Journey to SQL Authority with Pinal Dave