I am using the default SQL Server Maintenance task to reorganize index only which was running until I got the below error.

Executing the query "ALTER INDEX [PK_abc] ON " failed with the following error: "A severe error occurred on the current command. The results, if any, should be discarded.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

I have checked DBCC check db and no errors reported. Can this be due to low Transaction Log space as reorg don't consume space specially on data disk or I need to look at other direction. Any guidance would be greatly appreciated.

  • 1
    Have you tried running that command manually to see if you get the same error? Any errors in the SQL Error Log at the same time this occurred? That "severe error occurred" can happen for a number of reasons, corrupt DB, insufficient log or DB space, manually killed spid etc but each of the causes should log additional information. – HandyD Apr 19 at 22:23
  • I haven't tried to run it manually. What's baffling to me is that the job runs for approximate 30 minutes and throws that error but nothing is there on the error log.. The fragmentation level of the indexes are fine. I have low transaction log space but at least something should have been reported on the Error logs. – SQL_NoExpert Apr 20 at 13:01
  • Just restored the databases into another server, used ola scripts , did check db all went through...Space issue is the only thing that I can think of – SQL_NoExpert Apr 20 at 14:41

We can't say why, since you posted the SSIS error message. A maintenance plan is an SSIS package. SQL Server returned an error message to SSIS, and SSIS show you something else. You need to hunt down the SQL Server error message. Check the maintenance plan report file, assuming you have such. And the maintenance plan history table as well.

  • The above error was taken from the Error Log folder. The sql agent log has no info. – SQL_NoExpert Apr 19 at 17:02
  • Please be more precise. There's a folder named log. In there there's a file named error log. Again, check the report file for the main plan if you specified such. Also you can do history for the naint plan i ssms and in there see errors from sql server. – Tibor Karaszi Apr 19 at 17:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.