That makes more sense :-D.

Thanks for the feedback.

This is a great monitoring software. It...

Then run a log backup every 4-5 loops.

It'll get done eventually without killing the server.

The other option if you keep very little data is to export the data you want...

Take 30 minutes and read those 2 articles.

You'll understand exactly what's going on and how to fix it.

http://www.sqlservercentral.com/articles/64582/

http://www.sqlservercentral.com/articles/Transaction+Log/72488/

I'd make sure to debug that.

You might have a corrupt installation.

It's generally a bad idea and the wrong solution to the wrong problem.

So aside from the obvious than the log is taking more place than you want to, what is...

What was the error??

You can't downgrade a db like that.

You're taking a backup from 2008 R2 and trying to restore on 2008. That's never going to work (and it never has).

You can...

You might want to take a backup of the corrupt db as well before running repair. That way you can try again with other options in need be &...

... and maybe increase log backups frequency while the process runs.

ksnyder-1129141 (10/18/2011)

---

Aha! It was a trigger - there was a trigger on that table that was set up to track changes to the table.

I scripted...

adlakha.22 (10/18/2011)

---

@ninja's_RGR'us

ya...u was right.."world is full of surprises..."

like i again I got the surprise of 58 sec execution time:-D

and also seems result is not correct

u can see it from...

We have a lot of people with "plz do my work for me" type of question.

The let me google that for you answer pops...

Instead of trigger not made to handle multi rows is the most likely culprit.

Unless we're missing clues or the current assumptions are wrong.

ChrisM@Work (10/18/2011)

---

Couldn't help...