Skip to main content

Shrinking a SQL Server Log File with Database in Always ON Availability.


Shrinking a SQL Server Log File with Database in Always ON Availability.

                   Once we had a situation in our production server that the database which is in Always ON Availability group has been grown to the maximum size.

 Many of them say that we can't shrink the log file as the database is in Always ON and we should take the downtime to perform the operation. But we shrink-ed the database log file to 5 GB from 180 GB.

Steps are as below:

--To Check the Number of pages allocated by the LogFile.
DBCC LOGINFO

--To check the file sixe
sp_helpdb [SQLPantry]

--To check the Log file Size
DBCC SQLPERF(LOGSPACE)

The above statement will show the logspace of all db at present situation.

--To check the Log_reuse_wait description of a log file.
select log_reuse_wait_desc,* from sys.databases

The above statement will show the status of the log whether it has to be backuped i.e., LogBackup, Nothing, Active Transaction. 

When ever there is status as Active Transaction then we have to wait till the transaction has completed and start Backup Log and shrink the log file.

--Take a log backup.
Backup log [SQLPantry] to disk='D:\Backups\OnyxDevDaily\1.trn'

The above statement will be used to backup the log first and then start the shrinking of log file.
Atleast  3 or 4 time we have to take the log backups and start the shrink operation on it.

--To shirnk the log file after taking the backup. and run back to back.
--Log File has grown to the Szie of 3008457 GB


DBCC SHRINKFILE(2,300000)
DBCC SHRINKFILE(2,200000)
DBCC SHRINKFILE(2,100000)
DBCC SHRINKFILE(2,90000)
DBCC SHRINKFILE(2,80000)
DBCC SHRINKFILE(2,70000)
DBCC SHRINKFILE(2,60000)
DBCC SHRINKFILE(2,50000)
DBCC SHRINKFILE(2,40000)
DBCC SHRINKFILE(2,30000)
DBCC SHRINKFILE(2,20000)
DBCC SHRINKFILE(2,10000)
DBCC SHRINKFILE(2,5000)

The above statements are used to shrink the log file if the log has been increase to huge size then that has to be changed according to the requirement and perform it. 


--To check the open transactions on the Database


DBCC OPENTRAN()

Please check the new videos:


Shrinking of LDF and MDF Files on Drives
https://youtu.be/LtbSaiHu6Ho


Please Like, Subscribe, share the video for more videos...!!!



Comments

Unknown said…
This comment has been removed by the author.

Popular posts from this blog

Self Introduction and Responsibilities of a SQL Server DBA.

Hi, Self Introduction:                      I am Vang chew bigger , currently I am working with   Citronics , Here my role is SQL Server Database Administrator , I am having 3+ yrs Exp in SQL SERVER DBA with T-SQL, I have experience on SQL Server 2000, 2005 and 2008, I have a great experience on installation and configuration of SQL SERVER versions, and also applying the patches, hot fix, services packs and RTM’s accordingly, involved in upgrading on in place and side by side as per client requirement, and also Migrating the database on SQL SERVER 2000 to 2005 and 2008, Solid experience on configuring and maintenance of High availability SQL Server solutions, including Log shipping, Database Mirroring, Replication(Transactional and Merge) and SQL Server Clustering., having experience on performance tuning on server level, database level and query level, Responsible for working with application developers in identifying,...

Frequently Raised Errors in Log-Shipping

1. Question : IS it possible to log ship database between SQL 2000 & SQL 2008?  Answer: No, thats impossible, In SQL 2008 transaction log architecture is changed compared to SQL 2000 and hence you won’t be able to restore tlog backups from SQL 2000 to SQL 2008 or vice versa. 2. Question:I’m getting the below error message in restoration job on secondary server, WHY? [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set begins at LSN 7000000026200001, which is too late to apply to the database. An earlier log backup that includes LSN 6000000015100001 can be restored. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally. Answer: Was your sql server or agent restarted Y’day in either source or destination ? because the error states there is a mismatch in LSN. A particular tran log was not applied in the destination server he...