Thanks to Adiga. This fix is great.

Thanks Gary.

My issue fixed today after reading this thread.

A really good one. 🙂

palotaiarpad (7/19/2012)

---

I'm not agree with the "right" answer. I can revert to any undamaged snapshot:

Step 1: delete all other snapshot

Step 2: revert to the selected

The answer would be right only...

I am facing a deadlock issue. I can see application is sending update command on db and before that SPID is completed, it is sending the same command again, may...

Thanks Gila for making it specific. Yes, that is the required scenario. But my concern remain unanswered is - how exactly the update process will occur internally? All in one...

Agree with you.

Lowell - there could be always some lateral learnings. You write a script, I see how to write it. I am not into T-SQl by the way. And thanks for...

Thanks guys. I was busy in other things but this is still there and need to fix it. See, logshipping log backup job uses below command and it fails with...

Lowell, no. Both are production servers and exact same. No chance either of installing 'express with advanced' thing over there.

Any bode else? any idea?

Thanks for your reply. 'reading from the top' is not a concern. My purpose was to elaborate the problem. I will verify your code.

See you in part 2. This is...

for 'D1234', the first time it appears while reading from top, the value against it is 1001. I want this row in result. And skip the others if 'D1234' comes...

I am getting this error on SQL 2005 SP2 32 bit after configuring logshipping.

I am getting this error on SQL 2005 SP2 32 bit after configuring logshipping.

the answer is:

BACKUP LOG [DBNAME] TO DISK = N'D:\DBNAME_TRN\XYZ\DBNAME_20120803042046.trn' WITH NOFORMAT, INIT, NOSKIP, REWIND, NOUNLOAD, STATS = 10