Chat now with support
Chat with Support

Migration Manager for Email Archives 10.0 - SQL Guide

Virtualized infrastructure

There are important aspects to consider when installing SQL Server in a virtualized infrastructure. Follow the recommendations of the hypervisor vendor and Microsoft when sizing and configuring the environment.

The primary objective is to ensure that the resource requirements described above are dedicated to the virtual machine to ensure minimum impact to the performance from intermediate layers or co-existing guests.

The hypervisor should be type-1 (native) to ensure the minimum impact on hardware resource requirements.

Note the following general guidelines:

Maintenance Plans

There are three aspects of SQL Server Maintenance Plans to consider:

These will be described in the section below.

NOTE: The information provided is for guidance only. Often a SQL DBA team will have their own plans and procedures in place for applications relying on databases.

Database backups

We recommend that you perform regular backups of the Migration Manager for Email Archives Directory Database and the Item Databases. These databases contain important data relating to the configuration of the migration as well as the progress, down to the individual item level.

TIP: It is a best practice to perform nightly full backups of each of the databases. This will ensure the shortest recovery time.

Other backup types are supported; however, it may lengthen the recovery time if a database restore is needed.

Details for configuring database backups for specific versions of SQL Server is outside the scope of this document.

Index rebuilds

We recommend that you perform weekly index rebuilds on the Migration Manager for Email Archives Directory Database and each Item Database. This is particularly important when ‘Item Gathering’ is being performed where a large amount of data is being added to the Item Databases.

Migration Manager for Email Archives contains a new ‘Index Fragmentation’ page in the Admin Interface. This page shows the current levels of Index Fragmentation in the Migration Manager for Email Archives databases. This page also color-codes the rows to help highlight any potential problems, as follows:

Yellow – Page count > 1000, average fragmentation 10-30%

Red – Page count > 1000, average fragmentation >30%

TIP: Perform online Index Rebuilds in SQL Server weekly.

Details for configuring Index rebuilds for specific versions of SQL Server is outside the scope of this document. It is important to note that there are editions of SQL Server where the Index rebuild operation can be performed with the index online, and there are editions of SQL Server where the Index rebuild will cause the index to be made offline while the operation is performed. According to Microsoft documentation (referenced below), online index operations can be performed in SQL Server Developer Evaluation and Enterprise Editions.

http://technet.microsoft.com/en-us/library/ms186880(v=sql.105).aspx

If the edition of SQL Server in use for the migration does not support online index rebuilds, make sure to schedule the rebuild operations when there is a low level of activity from Migration Manager for Email Archives .

It is also recommended to do the 'Update Statistics' maintenance task, following an index rebuild.

NOTE: In many environments performance has been seen to dramatically increase if index rebuild and statistics updates are performed daily. Check the index fragmentation page frequently to see if this will help in a specific environment.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating