You need to restore ALL log backups, in sequence.

Yes, potentially large ones. Because it is not just tables in memory.

I don't know what the memory management's going to be, there's no info available on it yet.

Hekaton is...

Steve Jones - SSC Editor (8/5/2013)

---

GilaMonster (8/5/2013)

---

andrew gothard (8/5/2013)

---

:exclamation: you have no idea how happy I am that vendors do not...

And clients....

I remember...

What do you mean by 'mirror backup'?

If you mean, \BACKUP DATABASE... TO DISK ... MIRROR TO ... then that has nothing whatsoever to do with database mirroring.

If you do mean...

Jeff Moden (8/4/2013)

---

Remember being able to PIN TABLE and then took that wonderful feature away? Now they're bringing a form of it back with Hekaton but with more restrictions...

What do you mean by 'gaps in the tlogs'?

No, that would just increase the delay before a mirroring failover.

To reduce the impact of mirroring, reduce the latency of the hardening of the mirror's log records, that's the line's...

It can, yes.

Try changing the option SORT_IN_TEMPDB to ON

No, I'm giving you alternatives to using nolock. Which you use is up to you, all will give you accurate reports (accurate to specific points in time for some) without...

Try from management studio. If that fails, the object's lost.

kevin_nikolai (8/2/2013)

---

Normally you would use READ UNCOMMITTED in stored procedures of SQL Reports if they point

to Application server database - NOT to impact performance of the Application you would...

Script all objects, export all data, recreate the database, fix up your backup strategy.

The history table may well fail when exporting.