Hi muthukkumaran,

Earlier i was using continue_after_error syntax but later i used no_truncate and backup succeeded successfully.

I took tail log backup with no_trucate syntax as Gail suggested. I was able to take Tail Log backup and point in time recovery successfully done. Thanks all for your...

The command i issued to take Tail Log backup is :

backup log primer to disk='H:\primer.trn' with continue_after_error;

Gail, can you please let me know, then in which situations i can take Tail Log backup and in which situations I cannot take Tail Log backup ? What command...

Thanks guys..

So, I would not be able to take Tail Log backup if .mdf if missing.

Lowell somewhere on internet i read that we can take Tail Log backup if .ldf is not missing or corrupted or lost or deleted.

Yes I stopped the service, I just stopped and started the SQL service. Database had not showed any error when I started the SQL services again. I have not recreated...

Thanks all. 🙂

Muthukkumaran, thanks for your prompt reply, it really helped me. 🙂

Thanks for DCM it really helped.

If database is highly fragmented then how few users are using that database without any problem ?

Hi John,

I looked into log file and checked events log too. But could not get any information regarding slowness of db. What else I can do as I mentioned in...

If database needs reindexing then how another user is accessing the database in normal ways.

No, it does not. Is locally running on Node1. I can see it running in Services.msc.