SQL Server: Get the Current Size and Free Space of Data File and Log File



I recently discovered our application monitoring tool only looks at the total size of the data and log file.  In our case we had excessive database growth but the monitoring tool only knew how much the data file grew, not how much space the runaway process used up inside of the data file before the data file was forced to expand.

Below is a simple query which will allow you to get the current size of the data and log files along with the space still available.

 USE <YOUR DATABASE>

SELECT DB_NAME() AS Database_Name,
NAME FileName,
SIZE/128.0 Current_Size_MB,
SIZE/128.0 - FILEPROPERTY(NAME, 'SPACEUSED')/128.0 Free_Space_MB,
GETDATE() DateTime
FROM SYS.DATABASE_FILES;


First, use the function DB_NAME() with no parameter to get the name of the current database. Next, you will need the NAME and SIZE of the files from DMV SYS.DATABASE_FILES.

Name is the name of the file.

Size is the number of 8KB pages in the file.  Since a MB is 1024 KB, you divide the number of 8KB files by 1024/8 = 128 to get the size of the file in MB.

Use the FILEPROPERTY() function with the  name of the file and the file property 'SPACEUSED' to get the actual space used in the file. It is also returns a count of 8KB pages so divide by 128.0.

Next, subtract the SPACEUSED from the SIZE to get the available free space.

Finally, use the GETDATE() function for the date and time you collected the data.

Quick note, using 128.0 instead of 128 will implicitly cast the result as a float which will return a more precise calculation.  Do not use 128.0 if you are only interested in integer results but be aware you will be losing information.

Popular posts from this blog

Power BI Report Server: "An Error Has Occurred" or Power BI Report Server: "My Power BI Report is Coming up Blank" or Power BI Report Server: "401 and 403” Errors From Nowhere

Image
The information below is an extremely brief summary of the information collected to solve the elusive problem.  There are points I left out because I could not find supporting documentation and I did not want to release suppositions into the universe (why does an NTLM only issue impact a system using kerberos?).  I also want to thank my friend Josh Corrick for staying the course and seeing this through to the end.  See Josh's blog here:  https://corrick.io/blog/ Without warning, our Power BI Report Server began having issues presenting Power BI reports.   The reports would appear to render but would eventually return a blank report canvas.   There was not an error presented and this was impacting all Power BI reports.   An important note is the Power BI reports had worked as expected previously and no changes had been made to the report server such as upgrades or configuration changes. Subsequently, and seemingly unrelated, an error notification was presented when clicking
Read more

SQL SERVER 2017: STRING_AGG

STRING_AGG is a function released in SQL Server 2017.   The Oracle equivalent LIST_AGG has been available since 11gR2.  In the meantime, SQL Server users have resorted to black magic in order to get string values from separate rows. STRING_AGG is very welcome but there are some gotchas to be aware of.  Below is a simple example that works just like you think it would. SELECT STRING_AGG(FIrst_Name, ', ') WITHIN GROUP (ORDER BY First_Name) LIST FROM             (SELECT DISTINCT   First_name FROM [dbo].[Employee]     WHERE First_Name like 'A%' OR First_Name like 'B%') A ORDER BY LIST; You can run the query on any database you have string values and you will get something like this: A David, Aaren, Aaron, Abdul, Bob, Brian... If you want to split by the first letter of the name, do not make the mistake of using an over clause.  You will get an error stating STRING_AGG is not a window function. The function 'STRING_AGG' is not a valid win
Read more

Dynamic Label Positions With SSRS

Image
On a recent tabular "dashboard" with several bar charts in a small area our team found vertical positioning of the labels to be troublesome.  When the labels were set to "bottom" and the bar was too short the label would truncate the significant digits.  On the other hand, when the labels were set to "top" the numbers would be truncated if the column was too tall. Example of bar chart with label set to bottom. Same chart with the middle column label set to top. First we thought about using Smart Labels  but we quickly found that smart labels are not so smart when the labels are turned 90 degrees to make them vertical.  As you can see in the examples above the size of the numbers would make horizontal labels messy. So the obvious choice was to use a function to place the label on top when the bar was small and on the bottom once the bar was tall enough. In Report Builder, go to your chart and select a specific column - not just the chart.
Read more