i'm sorry fellas, i was so excited that i was able to fix the problem that it never occurred to me to save it......

how did i get...

so happy i'm not alone , sorry

PEOPLE, PLEASE HELP

this is just a beginning of sp4 rollout, tomorrow it can be your

problem too

in our shop we have close to 30 sql systems, mostly win2003

with the latest sp, and so on

out of 15 sql200 sp4 installations we have 2 failed

hanging in...

Thank you, very much! I'll try that.

Thank you very much MarkusB!

I thought may be there are ways around....

If not, ok tough luck

I expanded it trying to solve the problem.

Yep, sql 2000 sp3.

Recovery model: Full

Full backup 2 times a day, Trans log backup every 45 min.

Ok, here is a new stuff.

I have reboted the system, ran few dbcc cmds,

so, alocation problem has been rectified.

But I still have some indexes coruption.

When I'm rebuilding index it gives...

Yes Allen_Cui, i did.

It did not fix a problem.

vambati, the db has only one filegroup,

but contain 2 files in it (prim and sec)

for data and for log.

The autogrow is on.

After...

Thank you, very much!!!!!!!!!

Trans log grew up to 1.2 G.

Before and last time no trans were waited for the update. My fault, forgot to mention recovery mode was changed to simple...

How it can...

No FK involved and the column is not a part of comp index. Simple table, about 20 columns, clustered index and 2 none clustered. So, here is what happened: first...

Tried that already, same picture. Waited for

3 hours, lost my patience and canceled this

madness:)

So I'm going to try as was suggested above.

Thanks anyway!

Thanks again!!!!!!

Will try that on the weekend.

From my experience the main condition is there should be no users connecting to db in order to shrink it successfully.