Recording a maintenance history of your database

Recording a maintenance history of your database

Barrie Sosinsky, Contributor

Keeping records of your database activity is important to keeping it humming along. Corruptions can usually be traced to single entry or access. For the same reason you keep records of activity, you should also keep track of maintenance.

You can create a detailed summary of the actions that your maintenance plan took into a history table within the msdb database. It doesn't matter whether the msdb database is located on the server that stores the plan or another server of your choice.

You create this history by setting several options in the Database Maintenance Plan wizard. The first option is enabling the write history and specifying the location it is stored on. To place the history on the server where the plan is created, use the msdb.dbo.sysdbmaintplan_history

    Requires Free Membership to View

    By submitting your registration information to SearchSQLServer.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSQLServer.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Premium Access

Register now for unlimited access to our premium content across our network of over 70 information Technology web sites.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

This was first published in March 2005

Table on the Local Server. You can also limit the rows in the table using the second option in the wizard. If you set a size that is exceeded, SQL Server deletes the oldest data in the table and replaces it with the newest data, FIFO, or first in first out. Should you decide to record the history to a remote server, the third option in the wizard lets you do that by specifying the name of the server and the path to the msdb database that you want to use.

Barrie Sosinsky is president of consulting company Sosinsky and Associates (Medfield MA). He has written extensively on a variety of computer topics. His company specializes in custom software (database and Web related), training and technical documentation.


Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.

    Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.