Thanks

Is this indicative of an issue? Or memory pressure?

It will be in a restoring state after the tail log backup

This can be done by:

1. Run the restore job on DR server

2. Take a tail log backup on Production server - This will leave the database in a restoring state

3....

e90fleet (9/20/2013)

---

Hi all, question for you please:

i am upgrading sql from 2008 to 2012 and on one instance we have 3 databases setup with mirroring.

The plan is to use AAG...

Just to add to what Gail said. They're both part of the buffer pool...

As far as I know, this setup should not be a problem

Have you made any progress with it?

harikumar.mindi (8/13/2013)

---

Hi All,

I would like to find a way to find all types of locks which are more than 5secs and blocking processes which are for more than 10secs. I...

Regarding the log running restore job, you are probably dealing with extensive VLF fragmentation.

Run DBCC LOGINFO against the database in question to check how many VLF's you have

dedicatedtosql (7/17/2013)

---

Thank you very much for the reply. So all the memory that SQL Server process is taking up is called the Buffer Pool. In other words when we configure...

dedicatedtosql (7/16/2013)

---

Excellent article. The best part was the demo. I think in 2012 the actual execution plan it self shows tempDB spills with a warning sign on the SELECT operator....

TheSQLGuru (7/15/2013)

---

I think the author forgot a much better, more targeted option: RECOMPILE on the statement(s) INSIDE the sproc that are being screwed by parameter sniffing/plan caching. That...

dwilliscp (7/15/2013)

---

Good Article, but how do we tell what query is creating the spill over? I have been trying to figure out why a section of my job keeps taking...

Look at xp_delete_file or create a maintenance plan to remove the backup files which I am pretty sure uses xp_delete_file under the covers anyway.

Transaction log backups, whether it's from Log Shipping or some other processes taking log backups amounts to the same thing.

Yes you can.

Restore the previous nights backup and manually restore each transaction log up until the desired point.

You will however need to re-sync log shipping.