Scom Database Grooming Indexing Schedule error

In order to improve the efficiency of database access, we need to optimize the database, so here I would like to index my scom SQL collation.

When we created a plan for re-organizing indexes on the scom database in the maintenance plan for SQL, we found that the run always failed.

Found the error is this:

650) this.width=650; "height=" 439 "title=" clip_image001 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image001 "src=" http://s3.51cto.com/wyfs02/ M02/6d/e9/wkiom1vutk-r4_bvaagvonwbmhe402.jpg "border=" 0 "/>

Execute the query "ALTER index [pk__eventsta__95632343a552dfb0] on [E ...] failed with the following error:" Index ' pk__eventsta__95632343a552dfb0 ' was not found. ”。 The reasons for the failure may be that the query itself is problematic, the "ResultSet" property is not set correctly, the parameters are not set correctly, or the connection is not established correctly.

We know that the scom database is Operationsmanager and OPERATIONSMANAGERDW.

It is no problem to find the Operationsmanager database by separating and sorting the indexes separately, the problem is OPERATIONSMANAGERDW.

Then the analysis found:

650) this.width=650; "height=" 259 "title=" image "style=" margin:0px;border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/6D/E9/ Wkiom1vutldsckblaaibpwy-dl8741.jpg "border=" 0 "/>

So it caused the failure to say that the index ' pk__eventsta__95632343a552dfb0 ' could not be found.

Since the cause of the problem has been found, then we will exclude this paragraph.

650) this.width=650; "height=" "title=" clip_image003 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image003 "src=" http://s3.51cto.com/wyfs02/ M01/6d/e9/wkiom1vutlhjjyhnaadu5m2f2pe469.jpg "border=" 0 "/>

Re-execute found also reported error, said to find the index "PK_PERFORMA_AFAD0EB49338F10B"

Then the find still ruled out

650) this.width=650; "height=" 215 "title=" image "style=" margin:0px;border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02/6D/E9/ Wkiom1vutlgzggrjaafnwrwtnos497.jpg "border=" 0 "/>

Finally, we set up a new maintenance plan to exclude these 2 tables:

650) this.width=650; "height=" 484 "title=" clip_image005 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image005 "src=" http://s3.51cto.com/wyfs02/ M00/6d/e9/wkiom1vutlkc2accaafw6kwbyfs897.jpg "border=" 0 "/>

650) this.width=650; "height=" 484 "title=" clip_image006 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image006 "src=" http://s3.51cto.com/wyfs02/ M02/6d/e5/wkiol1vut_gtp6lraagywyjpn-w322.jpg "border=" 0 "/>

650) this.width=650; "height=" 484 "title=" clip_image007 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image007 "src=" http://s3.51cto.com/wyfs02/ M00/6d/e5/wkiol1vut_kcjdblaaf501zbeho752.jpg "border=" 0 "/>

650) this.width=650; "height=" 484 "title=" clip_image008 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image008 "src=" http://s3.51cto.com/wyfs02/ M01/6d/e5/wkiol1vut_kj93zfaahgrqrcidu589.jpg "border=" 0 "/>

650) this.width=650; "height=" 484 "title=" clip_image009 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image009 "src=" http://s3.51cto.com/wyfs02/ M02/6d/e5/wkiol1vut_bwfuqzaahustfbx1o106.jpg "border=" 0 "/>

650) this.width=650; "height=" 484 "title=" clip_image010 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image010 "src=" http://s3.51cto.com/wyfs02/ M00/6d/e5/wkiol1vut_ed2idaaae2gwbuacs690.jpg "border=" 0 "/>

650) this.width=650; "height=" 484 "title=" clip_image011 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image011 "src=" http://s3.51cto.com/wyfs02/ M00/6d/e9/wkiom1vutl-a6824aae16ca3n7o916.jpg "border=" 0 "/>

650) this.width=650; "height=" 484 "title=" clip_image012 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image012 "src=" http://s3.51cto.com/wyfs02/M01/6D/E9/ Wkiom1vutmdbs_sbaagdm1sdzwg531.jpg "border=" 0 "/>

This article is from the "Zjs Microsoft Desktop Virtualization" blog, so be sure to keep this source http://rdsrv.blog.51cto.com/2996778/1657925

Scom Database Grooming Indexing Schedule error