January 19, 2011 at 2:10 pm
My daily maintenance plan quit running the other day. I was able to track down the problem. The reorganize index and update statistics fails on 3 tables. I am not sure why these tables are a problem now since they have worked fine in the past. I cannot find any evidense that these tables are corrupt. I have the plan run at 10:00pm after everyone has left. What can I do to get these tables to run clean in the maintenance package?
Thanks
Quinn
January 19, 2011 at 3:40 pm
Please check the maintenance plan log file to find the actual reason for the failure.
Thank You,
Best Regards,
SQLBuddy
January 20, 2011 at 3:50 am
Please post the exact error message.
M&M
January 20, 2011 at 8:12 am
Thanks for the help.
Here is the error I am getting.
Error number: -1073548784
Executing the query "ALTER INDEX [PK_ActiveSubscriptions] ON [dbo].[Act..." 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.
This one too.
Executing the query "ALTER INDEX [a2_ix1] ON [dbo].[DEMS] REBUILD PARTI..." 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.
Thanks
Quinn
January 20, 2011 at 8:36 am
I had taken the 2 DB's that were having trouble with certain files out of the maintenance plan so they would run. I just put them in to see if I could get the error on update statistics and there doesn't seem to be any occuring.
Also as long as we are talking about MP's. We had a contractor remote in to install a new DB and they did a restore to add the DB to the server. I can see the DB in SSMS but when I go to add the DB to the MP I cannot back up the log file it isn't listed in in the list of DB's available for that step. What would cause that?
Thanks
Quinn
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply