Home » SQL ServerRSS

Rebuild Index Error -1073548784

I am getting the following error on Rebuild Index Maintenance Task.

"Executing the query "ALTER INDEX [PK_cartrige] ON [dbo..." failed with the following error: "A severe error occurred on the current command.  The results, if any, should be discarded.
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."

Where can i find more details on troubleshooting this error and find more details on the error. It seems to be a persistant problem since sql server 2005.

Details:

-Maintenance Plan has been working well for months. -Std Edition Sql Server 2008 -Db Integrity check successfull -sort result in tempdb is off -keep index online while reindexing is off -local server connection works for all other jobs prior to the task
 

2 Answers Found

 

Answer 1

It's standard operating procedure these days to just Google (Bing!) any error message like this.

I have no idea offhand what it means but it seems awfully common.

http://www.google.com/#sclient=psy&hl=en&site=&source=hp&q=Rebuild+Index+Error+-1073548784&aq=f&aqi=&aql=&oq=&gs_rfai=&pbx=1&fp=1fcdface22984313

http://social.msdn.microsoft.com/Search/en-US?query=Rebuild%20Index%20Error%20-1073548784&refinement=49&ac=8

http://social.msdn.microsoft.com/forums/en-us/sqldatabaseengine/thread/29C30F2A-DEF6-469A-BAE1-966FAB8E4E2D

seems to relate to the transaction log being full, maybe you're out of disk space entirely.

is your database set to simple or full recovery?

Josh

 

 

Answer 2

Your absolutly right, the db was on full recovery mode and that was causing the logs to grow.

for now i had to babysit the backup and issued a checkpoint, and the rebuild was successfull. I'm looking into it and will add details. However, the logs should have grown without any problem as there was enough space. I am suspecting the authogrowth factor was not appropriate for the task.  Thanks Josh

 
 
 

<< Previous      Next >>


Microsoft   |   Windows   |   Visual Studio   |   Follow us on Twitter