When using SQL Server, you may want to find file information to gather statistics you can use to make database management decisions.
This is when you may wish to use sys.master_files. This single, system-wide view contains a row for each file of a database as it is stored within the master database. It holds file information for all the databases in a SQL Server instance.
Also known as a system catalog view, sys.masterfiles can be used in lieu of sp_helpfile and actually returns more information.
sys.master_files is an offshoot of master database tables, which were physical tables in a pre-SQL 2005 master database that could be accessed and manipulated. It is now available in SQL Server 2008 through the most current version of SQL Server.
Those master database tables are now protected and available for viewing only as an object of the resource database.
A user has several options available when using sys.master_files. He/She can select all the server’s database files, but can also view specific files based on their size or physical locations. This might, for example, be used to return all the database files on a physical drive.
The results returned can also be sorted and ordered by file name. The view contains other information, such as the database file’s state and size—including the maximum file size—and whether it is a log or a data file.
Ford suggests using the following simple SQL code when using sys.master_files rather than relying on SELECT *:
SELECT DB_NAME(database_id) AS database_name , database_id , [file_id] , type_desc , data_space_id , name AS logical_file_name , physical_name , (SIZE*8/1024) AS size_mb , CASE max_size WHEN -1 THEN 'unlimited' ELSE CAST((CAST (max_size AS BIGINT)) * 8 / 1024 AS VARCHAR(10)) END AS max_size_mb , CASE is_percent_growth WHEN 1 THEN CAST(growth AS VARCHAR(3)) + ' %' WHEN 0 THEN CAST(growth*8/1024 AS VARCHAR(10)) + ' mb' END AS growth_increment , is_percent_growth FROM sys.master_files ORDER BY 1, type_desc DESC, [file_id];
What the code above creates is a basic query containing the database name and ID. It also shows the file’s logical and physical name, the file type, the data_space_id, and also the file’s size and growth settings.
From this point, the results can be filtered and manipulated. This is useful for easily discovering those files using auto growth settings, among other things. It eliminates the need to use stored procedures and enables you to access the information without needing more coding.
Microsoft also notes:
If you need help with this or other SQL Server issues beyond the scope of this post, please contact Datavail for more information on how our expert SQL Server DBAs can best support you and your organization with custom solutions tailored to your specific SQL Server needs.
EPM applications help measure the business performance. This post will help you choose the best EPM solutions for your organization’s needs and objectives.
It’s 2015 and you can now establish totally respectable MS SQL DBA credibility just by mentioning you have been in the game since SQL Server version 9. You may even get the same gasps of shock from some colleagues that used to be reserved for the version 6 veterans.