Disconnect error while running re-indexing job.

Hi,
I have a 24Gb database with half a dozen indexes against various
tables which is failing during the reindexing task (as part of the
maintenance plan) at least 80% of the time.
The error given in the logs is:
"[Microsoft SQL-DMO (ODBC SQLState: 01000)] Error 0: This server has
been disconnected. You must reconnect to perform this operation."
Now, I am aware that this means the server disconnected or became
unavailable during the re-indexing, but I cannot find any logical
reason why this should happen. There are no access violations, either
in the SQL logs or the event viewer. No-one manually stopped SQL
Server. No other part of the maintenance plan has any issues. There
are no other errors around the time of this failure.
If anyone has any suggestions as to why this might be occurring, I'd
be grateful to hear them.
Thanks in advance,
Andy.
One of the things I would check is the autogrow/autoshrink options... If
those options are enabled AND your database picks an inopportune time to
grow (or shrink) errors like that are possible.
Steve
"Andy D." <clotho42@.yahoo.com> wrote in message
news:279509a6.0404260826.2b769d01@.posting.google.c om...
> Hi,
> I have a 24Gb database with half a dozen indexes against various
> tables which is failing during the reindexing task (as part of the
> maintenance plan) at least 80% of the time.
> The error given in the logs is:
> "[Microsoft SQL-DMO (ODBC SQLState: 01000)] Error 0: This server has
> been disconnected. You must reconnect to perform this operation."
> Now, I am aware that this means the server disconnected or became
> unavailable during the re-indexing, but I cannot find any logical
> reason why this should happen. There are no access violations, either
> in the SQL logs or the event viewer. No-one manually stopped SQL
> Server. No other part of the maintenance plan has any issues. There
> are no other errors around the time of this failure.
> If anyone has any suggestions as to why this might be occurring, I'd
> be grateful to hear them.
> Thanks in advance,
> Andy.

Disconnect error while running re-indexing job.

Hi,
I have a 24Gb database with half a dozen indexes against various
tables which is failing during the reindexing task (as part of the
maintenance plan) at least 80% of the time.
The error given in the logs is:
"[Microsoft SQL-DMO (ODBC SQLState: 01000)] Error 0: This server has
been disconnected. You must reconnect to perform this operation."
Now, I am aware that this means the server disconnected or became
unavailable during the re-indexing, but I cannot find any logical
reason why this should happen. There are no access violations, either
in the SQL logs or the event viewer. No-one manually stopped SQL
Server. No other part of the maintenance plan has any issues. There
are no other errors around the time of this failure.
If anyone has any suggestions as to why this might be occurring, I'd
be grateful to hear them.
Thanks in advance,
Andy.One of the things I would check is the autogrow/autoshrink options... If
those options are enabled AND your database picks an inopportune time to
grow (or shrink) errors like that are possible.
Steve
"Andy D." <clotho42@.yahoo.com> wrote in message
news:279509a6.0404260826.2b769d01@.posting.google.com...
> Hi,
> I have a 24Gb database with half a dozen indexes against various
> tables which is failing during the reindexing task (as part of the
> maintenance plan) at least 80% of the time.
> The error given in the logs is:
> "[Microsoft SQL-DMO (ODBC SQLState: 01000)] Error 0: This server has
> been disconnected. You must reconnect to perform this operation."
> Now, I am aware that this means the server disconnected or became
> unavailable during the re-indexing, but I cannot find any logical
> reason why this should happen. There are no access violations, either
> in the SQL logs or the event viewer. No-one manually stopped SQL
> Server. No other part of the maintenance plan has any issues. There
> are no other errors around the time of this failure.
> If anyone has any suggestions as to why this might be occurring, I'd
> be grateful to hear them.
> Thanks in advance,
> Andy.

Disabling triggers not involved in replication in SQL 2000

I am experimenting with replication and recently set up a prototype
transactional replication with about a dozen publications and perhaps twice
as many articles. All has gone smoothly so far. One item that is causing
much gnashing of teeth is the fact that I cannot disable a pre-existing
trigger that has nothing to do with the replication.
Msg 4929, Level 16, State 2, Line 1
Cannot alter the table 'XXXXX' because it is being published for replication.
Any help greatly appreciated.
Craig
Craig,
you won't be able to do this sort of statement: "alter table suppliers
disable trigger all" but you can issue an alter trigger statement. If there
are only a few triggers this might be practical for you.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)