Nowadays, databases are used almost everywhere: Business divisions, application development teams and even webmasters use databases to store dynamically changing information. One of the most common database management systems (DBMSs) is Microsoft SQL Server.
SQL database administrators often need to estimate how large a database is. For example, if a database is too large for the enterprise, it might need to be normalized; if the size is less than expected, you might be able to denormalize the database to improve query performance. In general, massive databases require strong hardware, or at least a lot of space, so it is normal to see file size be restricted. It’s particular important to monitor the size of test and development databases, since the log files can be even bigger than the database files, and the resulting volume of data can trigger significant problems.
If you need to check a single database, you can quickly find the SQL Server database sizein SQL Server Management Studio (SSMS): Right-click the database and then click Reports -> Standard Reports -> Disk Usage. Alternatively, you can use stored procedures like exec sp_spaceused to get database size. However, both of these methods will show you the size of only a single database. To process all databases on SQL Server, you have to use T-SQL queries, which are complex and require more extensive scripting skills.
Using Netwrix Auditor for SQL Server, you can get database size in a few clicks, along with other key details like database state, location and last full backup data. Moreover, Netwrix Auditor provides invaluable actionable intelligence about your Microsoft SQL Server, including who has access to what, who’s logging in and what critical changes are being made. As a result, you can easily conduct regular SQL Server auditing to mitigate the risk of a data breach, spot privilege abuse, prove IT compliance and maintain high database availability.
