Advertisement

12.27.2007 at 02:40PM PST, ID: 23046088
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.4

SQL SERVER - Understand the maintenance report

Asked by donpick in MS SQL Server

Tags: , , ,

Running Small Business Server 2003 premium which includes SQL Server 2000.  All fully patched.

Maintenance plans are new to me.  As you experts know you can build a plan to check database integrity.  (see report below).  The process failed because, it seems, the Maintenance Plan (mp) cannot put some databases into single user mode.  Why not?  No one is using the databases at 3:30 am.  

My question: What do you experts do?  
-      Do you ignore mp and use your own code to check database integrity?
-      If not, how do you tell SQL Server to put certain databases into single user  mode before performing the integrity check?  I didnt see an option to do this when I built the plan.

-      If you build you own, could you kindly share some code?

Thank you.

======================  The Maintenance report ==============

Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server 'SBS2003SERVER\INVEST' as 'DONHOME\SQLServerAdmin' (trusted)
Starting maintenance plan 'INVEST_plan' on 12/26/2007 3:30:01 AM
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5058: [Microsoft][ODBC SQL Server Driver][SQL Server]Option 'SINGLE_USER' cannot be set in database 'MASTER'.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
[1] Database master: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: [Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not processed. Database needs to be in single user mode.

    The following errors were found:

[Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not processed. Database needs to be in single user mode.
    ** Execution Time: 0 hrs, 0 mins, 1 secs **

[2] Database model: Check Data and Index Linkage...

    ** Execution Time: 0 hrs, 0 mins, 1 secs **

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070: [Microsoft][ODBC SQL Server Driver][SQL Server]Database state cannot be changed while other users are using the database 'msdb'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
[3] Database msdb: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: [Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not processed. Database needs to be in single user mode.

    The following errors were found:

[Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not processed. Database needs to be in single user mode.
    ** Execution Time: 0 hrs, 0 mins, 1 secs **

[4] Database StockData: Check Data and Index Linkage...

    ** Execution Time: 0 hrs, 0 mins, 33 secs **

Deleting old text reports...    0 file(s) deleted.

End of maintenance plan 'INVEST_plan' on 12/26/2007 3:30:34 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Start Free Trial
[+][-]12.27.2007 at 03:49PM PST, ID: 20538389

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: MS SQL Server
Tags: Microsoft, SQL Server, 2000, Understand the maintenance report
Sign Up Now!
Solution Provided By: pai_prasad
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20080924-EE-VQP-38 / EE_QW_2_20070628