Increase in the Growth of the SQL Server Log File.

There are many reasons which cause the SQL Server Log file to grow to unbelievable size i.e., the space available in the Disk.

1. whenever we have not scheduled a Log_backup on the server the log file size grows bigger and occupies the disk on the specific drive.
2. If we have any repplication setup. Then we will be have log file growth.
3. Due to long running transaction also that causes the Log file grows.

All the transactions that are performed on the SQL are done at the log files, after a commit transaction i.e.., from code or the SQL Server check point the data is updated to the Data file of the database.

To Check the Growth of the Database Log files.

DBCC SQLPERF(LOGSPACE)

The Log Size (MB) column shows the size of the log files
The Log Space Used(%) column shows how much of the log space is used by the SQL Server Log Files.

Example:

In some environment we will be able to see the below

Log Size (MB): 43562.19
Log Space Used: 1000.45

When ever we take the Standard reports on the SQL Server we can see the following.
Total Space Use: 43562.19 MB
Data File Space Use: 847.88 MB
Transaction LogUse: 42714.31 MB

By the above figures we can see that only 188 MB is used by the log File. The The 42 GB space is empty. So we can release the space so that it can be accommodated to the disk. It can be used by the SQL Server for usage to store the data on the disk.

Comments

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, resolving and proactively working to prevent performance or oth

SQL Server 2016 Windows Server 2016 Firewall Rule Step-By-Step.

SQL Server 2016 Windows Server 2016 Firewall Rule Step-By-Step. Opening Firewall in SQL Server 2016. Once the SQL Server is installed on the machine. We must enable the incoming traffic i.e., from the application to the SQL Server Database. For this purpose, we must create rule for SQL Server ports so that the application can connect to database & perform the CRUD operations on the tables. Now Let’s start Step-by-Step to enable it. 1. Start System and Login (As Administrator); 2. Open Control Panel. Click on Windows Firewall; 3. Now click on Advanced Settings; 4. Windows Firewall console open. If you click on Properties (right side) – you can disable firewall for all networks. We going to Inbound Rules (left side) for our rule creation; After Clicking on the Inbound rules. We will see the below screen. Click on New

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 Activ

MS SQL SERVER DBA

Search This Blog