WEBVTT

00:06.070 --> 00:13.010
This leader we are going to take a look at how we can verify the size of the mailbox databases.

00:13.030 --> 00:17.840
This is fairly simple and the information can be easily retrieved.

00:17.860 --> 00:19.920
You don't get mailbox database.

00:19.930 --> 00:21.920
Come on let this reader reveal.

00:22.030 --> 00:29.260
Take a look at how to report on mailbox database size using the Exchange management shell for exchange

00:29.260 --> 00:34.510
2006 team to retrieve the total size for each mailbox database.

00:34.630 --> 00:36.380
Use the following command.

00:36.550 --> 00:45.470
Get mailbox database destitutes and pipe it to a select object certain by name and database size their

00:45.490 --> 00:48.590
output for this command will look like mine.

00:48.730 --> 00:52.070
They've got name calling and database size going.

00:52.180 --> 01:00.290
Now one run to get mailbox database commands that we can use the state or switch parameter to receive

01:00.340 --> 01:08.230
additional information about the database such as Mount St. Louis Lebec upstaters and the total size

01:08.230 --> 01:15.910
of the database as shown in the previous example to generate a report with this information simply pipe

01:15.910 --> 01:23.230
the command to the experts this week a month left and specify the path and file name has shown that

01:23.230 --> 01:27.790
misfeature to the IAC and show the example.

01:27.820 --> 01:36.820
So we've got get mailbags mail box database with status parameter and pipe it to select object certain

01:36.820 --> 01:45.640
by name server database size mounted state and pipe it to experts since we specify the paths to the

01:45.640 --> 01:46.500
file.

01:46.510 --> 01:53.390
In my case it's Seacole on backslash database report that says we lose time we are divided.

01:53.440 --> 01:57.060
The server name and mounted information.

01:57.070 --> 02:04.720
So we've got Saro name that the database is currently associated with and the MT status for their database.

02:04.720 --> 02:12.940
When we are in the well for the database size you probably noticed that we see the total size of megabytes

02:12.940 --> 02:21.070
and in parenthesis we see the value in bytes rather than just say in a single intermural for the total

02:21.070 --> 02:21.750
size.

02:21.810 --> 02:30.550
The database size property is of the type byte quantified size and we can use several methods provided

02:30.550 --> 02:34.010
by this type to convert the value.

02:34.180 --> 02:42.830
If all we want is to retrieve a numeric representation of the database size for example we can use the

02:43.100 --> 02:54.070
two kilobyte to be to G-B and 2 TB methods of the database size subject to convert the well to kilobytes

02:54.100 --> 02:57.310
megabytes gigabytes or terabytes.

02:57.310 --> 03:00.360
For example we can type the following command.

03:00.490 --> 03:09.730
Get mailbox database stateliest and pipe it to select object certain by name and add in a custom property

03:10.030 --> 03:14.770
where we want our database size in megabytes.

03:14.770 --> 03:21.270
As you can see this time we have created a calculated property for the database size and we are using

03:21.270 --> 03:26.980
only 2 megabyte method to convert the value of the database.

03:26.980 --> 03:31.740
The output we get from that command would look something like mine.

03:31.780 --> 03:37.930
We get database name column and database size in megabytes.

03:37.930 --> 03:44.530
This technique may be useful if you are looking to generate a basic reports that you don't need to have

03:44.560 --> 03:48.710
all of the extra information that is returned by default.

03:48.730 --> 03:56.200
For instance you may already know that your databases will always be in the range of hundreds of gigabytes.

03:56.200 --> 04:03.880
You can simply use a calculated property as shown in the previous example and called to and call the

04:04.120 --> 04:07.990
two G-B Masset for each database size Sobchak.
