IBM Version 52 Computer Accessories User Manual


 
Microsoft SQL Server maintenance plans can be configured by a wizard in
Microsoft SQL Server Management Studio, which can help alleviate some of the
burden involved in creating the plan. In Microsoft SQL Server Database Engine,
maintenance plans create an Integration Services package, which is run by an SQL
Server Agent job. The goal of a maintenance plan is to:
v Back up the Sterling B2B Integrator database regularly using either the simple
model or the full recovery model
v Update the statistics on all Sterling B2B Integrator tables and associated indexes
v Rebuild or reorganize indexes on Sterling B2B Integrator tables
v Run database consistency checks
For more information about MS SQL Maintenance Plans, see the Microsoft
Developer Network Web site: https://msdn.microsoft.com/en-us/library/
ms187658%28v=sql.105%29.aspx
You can use either the simple recovery model or the full recovery model with the
database. If you are unsure about which model to use, use the full recovery model.
Consider the simple recovery model if you are agreeable to the following:
v Point of failure recovery is not necessary. If the database is lost or damaged,
you are willing to lose all the updates between a failure and the previous
backup.
v You are willing to risk the loss of some data in the log.
v You do not want to back up and restore the transaction log, preferring to rely
exclusively on full and differential backups.
v You are willing to perform a differential database backup every day and a full
database backup over the weekends (during low activity period).
For more information about Backup Under the Simple Recovery Model, see the
Microsoft Developer Network Web site: https://msdn.microsoft.com/en-us/
library/ms191164%28v=sql.105%29.aspx or https://msdn.microsoft.com/en-us/
library/ms186289%28v=sql.105%29.aspx
Consider the full recovery model if you are agreeable to the following:
v You want to recover all the data.
v You want to recover to the point of failure.
v You want to be able to restore individual pages.
v You are willing to incur the cost of additional disk space for transaction log
backups.
v Performance of transaction log backups every 30-45 minutes.
For more information about Backup Under the Full Recovery Model, refer to the
Microsoft Developer Network Web site, which can be accessed from:
https://msdn.microsoft.com/en-us/library/ms186289%28v=sql.105%29.aspx.
For more information about Transaction Log Backups, refer to the Microsoft
Developer Network Web site, which can be accessed from: https://
msdn.microsoft.com/en-us/library/f4a44a35-0f44-4a42-91d5-d73ac658a3b0
%28v=sql.105%29 .
Note: The Microsoft Developer Network Web site links provided access pages for
Microsoft SQL Server 2008 R2. To view pages for other versions, such as Microsoft
SQL Server 2012, use the Other Versions feature on the viewed page.
Performance Management 59