The SQL database requires regular maintenance and back ups to ensure that McAfee ePO functions correctly.

The McAfee ePO SQL database houses everything that McAfee ePO uses to function; your System Tree structure, policies, administrators, client tasks, and configuration settings.

Back up your SQL database regularly, in case your SQL database or your McAfee ePO server environment fails. If the McAfee ePO server must be rebuilt or restored, current back ups ensure that a safe copy is available. In addition, if you are using the information in the Microsoft website, Full Database Backups (SQL Server) (https://msdn.microsoft.com/en-us/library/ms186289.aspx), your transaction log can continue to grow indefinitely until a full backup is performed.

Table data fragmentation

One of the most significant performance problems found in databases is table data fragmentation. For example, table fragmentation can be compared to an index at the end of a large book. One index entry in this book might select several pages scattered throughout the book. You must then scan each page for the specific information you are looking for.

This fragmented index is different from the index of the telephone book that stores its data in sorted order. A typical query for the name "Jones" might span multiple consecutive pages, but they are always in a sorted order.

For of a database, you start with the data looking like a telephone book and, over time, end up with the data looking more like a large book index. You must occasionally resort the data to re-create the phone book order. This is where reindexing and rebuilding your McAfee ePO SQL database is critical. Over time your database becomes more fragmented, especially if it manages a larger environment where thousands of events are written to it daily.