data-konzept

'As a Database Administrator I frequently encounter the need to look into the sizes of my databases at both the database level (aggregating the log file and all the data files that comprise the larger database) or the file level. Sometimes I need this information for all the databases and sometimes just a single database. While there are options to collect this information there is not a single pane of glass that exposes all the metadata points that are of interest to me. Why do I care? When will I need this information? Let's consider the questions that can be answered with this sort of information:

• Which databases are my biggest consumers of storage?
• Are any of my databases' files using percentage as a measure of growth for auto-grow events?
• Am I seeing any situations where my transaction logs are sized incorrectly for the size of my database?
• What are my largest transaction logs?
• Are the data files for tempdb sized the same and with the same growth settings?
• Am I getting close to filling up any of my data files or log files?
• Are my data (or log) files hosted on an incorrect drive?'...

http://sqlmag.com/database-administration/quickly-identify-database-and-file-sizing-any-sql-server-instance