Acronis Backup for Windows Server Essentials - User Guide - Manual (Page 282)

282 Copyright © Acronis International GmbH, 2002-2014
Create Table ##temp
(
DatabaseName sysname,
Name sysname,
physical_name nvarchar(500),
size decimal (18,2),
FreeSpace decimal (18,2)
)
Exec sp_msforeachdb '
Use [?];
Insert Into ##temp (DatabaseName, Name, physical_name, Size, FreeSpace)
Select DB_NAME() AS [DatabaseName], Name, physical_name,
Cast(Cast(Round(cast(size as decimal) * 8.0/1024.0,2) as decimal(18,2)) as
nvarchar) Size,
Cast(Cast(Round(cast(size as decimal) * 8.0/1024.0,2) as decimal(18,2)) -
Cast(FILEPROPERTY(name, ''SpaceUsed'') * 8.0/1024.0 as decimal(18,2)) as
nvarchar) As FreeSpace
From sys.database_files'
Select * From ##temp
drop table ##temp
Determining locations of database files by using SQL Server Management Studio
Default locations
SQL Server database files are in their default locations unless you have customized the paths
manually. To find out the default locations of database files:
1. Run Microsoft SQL Server Management Studio and connect to the necessary instance.
2. Right-click the instance name and select Properties.
3. Open the Database Settings page and view the paths specified in the Database default locations
section.
Custom locations
If SQL Server database file locations were customized, proceed as follows.
1. In Microsoft SQL Server Management Studio, expand the necessary instance.
2. Right-click the database, and then click Properties. This will open the Database Properties dialog
box.
3. In the Select a page pane, click Files and view the paths specified in the Database files section.
11.1.1.2 Exchange Server database files
Exchange databases have three types of files:

Database file (.edb)
Contains message headers, message text, and standard attachments.
An Exchange 2003/2007 database uses two files: .edb for text data and .stm for MIME data.

Transaction log files (.log)
Contains the history of changes made to the database. Only after a change has been securely
logged, it is then written to the database file. This approach guarantees a reliable recovery of the
database in a consistent state in case of a sudden database interruption.
Each log file is 1024 KB in size (or 5120 KB in Exchange 2003). When an active log file is full,
Exchange closes it and creates a new log file.

Checkpoint file (.chk)