You'll have to register, and I give no warranty as to how workable this is: however, it's taken me half an hour to find the scdw_reindex1.zip or the scdw_reindex.zip file, so I thought I'd link.
Showing posts with label Rebuild Index. Show all posts
Showing posts with label Rebuild Index. Show all posts
Thursday, 19 August 2010
SystemCenterReporting Reindex Script
Can be found here. It was referred to here and here, however, the links within those pages are no longer extant.
Monday, 4 January 2010
sp_fulltext_catalog
And a happy new year to you. Mine started like this (among other issues), with an error for an hourly rebuild index job.
USE [thisdatabase]
EXEC sp_fulltext_catalog
N'this_database_index' ,
N'start_full'
Gave this result
Executed as user: Machinename\SQLAdmin. Execution of a full-text operation failed. The Gatherer is shutting down. [SQLSTATE 42000] (Error 7619). The step failed.
The Gatherer? You what?
This was on a non-clustered SQL 2000 box (8.0.2055), and the solution was to restart MSSeach. This I did via Services Administration, where it is helpfully labelled as 'Microsoft Search'. I have no idea what The Gatherer was, or did, or does, but it seems to be happy now.
USE [thisdatabase]
EXEC sp_fulltext_catalog
N'this_database_index' ,
N'start_full'
Gave this result
Executed as user: Machinename\SQLAdmin. Execution of a full-text operation failed. The Gatherer is shutting down. [SQLSTATE 42000] (Error 7619). The step failed.
The Gatherer? You what?
This was on a non-clustered SQL 2000 box (8.0.2055), and the solution was to restart MSSeach. This I did via Services Administration, where it is helpfully labelled as 'Microsoft Search'. I have no idea what The Gatherer was, or did, or does, but it seems to be happy now.
Tuesday, 18 August 2009
Rebuild Index Failed
"failed with the following error: "Online index operations can only be performed in Enterprise edition of SQL Server.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly."
Or, perhaps, the failure reason is that the SQL Server in question is Standard Edition, and that's pretty much it?
Other suggestions here (if you're not in Standard Edition!).
It would be nice, though, if SQL were clever enough to know when it's running Standard Edition, and not give you the option of an Online Index Operation when you're building the maintenance plan, now wouldn't it?! Or is that a Moon-on-a-Stick request?
Or, perhaps, the failure reason is that the SQL Server in question is Standard Edition, and that's pretty much it?
Other suggestions here (if you're not in Standard Edition!).
It would be nice, though, if SQL were clever enough to know when it's running Standard Edition, and not give you the option of an Online Index Operation when you're building the maintenance plan, now wouldn't it?! Or is that a Moon-on-a-Stick request?
Subscribe to:
Posts (Atom)