By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,856 Members | 2,179 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,856 IT Pros & Developers. It's quick & easy.

Reindex maintenance plan fails after adding secondary data file

P: n/a
Hello all, I have a SQL 2000 Standard SP3 install. I was running low on
free space so added a secondary data file on a separate hard drive. I
did this for each of two databases.

Since then, and I guess it could be only a coincidence, my weekly
reindex maintenance plan has been failing, but only for one of the two
databases I added the secondary file to.

The 1st weeks emailed report shows that it rebuilds indices for 12
tables and then tries to rebuild indexes for a table named 'call'. At
that point the report shows:
[Microsoft SQL-DMO (ODBC SQLState: 01000)] Error 0: This server has
been disconnected. You must reconnect to perform this operation.
The job locked up and only finished when another job ran which turned
on full logging using an alter database command.

The 2nd week I ran a trace and at the crucial point it captured this
SQL:BatchStarting dbcc dbreindex(N'[dbo].[call]', N'', 90,
SQL:BatchStarting SELECT N'Testing Connection...'

The first batch never completes and lots of 'Testing Connection'
commands occur until the job is aborted.

A DBCC CHECKDB command shows no errors. Can anyone help me with what
could be causing the disconnected state with that table and how to
remedy it


Jul 23 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.