all looks ok to me - mostly

here's a test for you to perform (i have a suspicion i know what the problem is)

open up management studio and open 4 query...

i have no idea what the difference is between...

On one of the three server pairs in question, yes the hotfixes don't match (2282+2187, and I am awaiting clearance to patch)...and of the four times we have had this...

ps - it was fixed in a service pack version - but since it's sql2000 which i haven't used for 6 years i have no idea which one

GilaMonster (4/25/2012)

---

How can you do an index defrag of a log shipping secondary? It's read-only at best. Or do you mean index rebuild on the primary and log shipping copied...

index defrag

by the way -

FCB stands for File Control Block, the physical file structure used

by SQL to write in and read data from the storage.

i've had these before...

http://support.microsoft.com/default.aspx?scid=kb;en-us;815183

the error Could not open FCB for invalid file ID %d in database '%.*ls'. is know to cause data corruption, thread errors and runtime errors

are there different service pack versions...

it would be easier if you put in the post the names of the 2 files so we can see the difference

there's a whole list of "non-batch breaking" errors listed on the microsoft site - most of them are pretty unusual - but some are quite alarming (such as foreign key...

i just found a whole bunch of other sites where this is a known issue by googling Jet 4.0 first rows

the actual number of sample rows is 8

more info as...

i had this problem before - have a look in the registry under the Jet 4.0 engine settings and there is a registry value that is used to "automatically determine"...

here is the link

http://www.youtube.com/watch?v=U_Kle3gKaHc

check your wait stats and see what the bottleneck is

if you haven't already then go on youtube and look up brent ozar's wait stats video which will explain how to...

you might want to check this slightly differently...... haven't...