SQL manages its own memory very well. There's a hell of a lot to it. If you want the details, get a copy of "Troubleshooting SQL Server: A guide for...

If that's what the documentation says, then that's what it can take.

Cody K (4/3/2014)

---

- I'm not sure what the benefit would be for the programmers to go through an ORM layer to translate arbitrary XML data into a column format, if...

Koen Verbeeck (4/3/2014)

---

GilaMonster (4/3/2014)

---

Jeff Moden (4/2/2014)

---

Koen Verbeeck (4/2/2014)

---

GilaMonster (4/1/2014)

---

In-memory OLTP (hekaton) is for heavy concurrent load (tens of thousands of concurrent connections with thousands of inserts/sec). The advantage is the...

The documentation is correct (unsurprising)

Pro: flexible

Cons: Performance, no data integrity, misuse of a relational structure (sounds like they want a schema-less database, one of the NoSQL variants), hard to manage

When you would use it:...

By design, normal, documented behaviour. SQL will take all the memory it is allowed to use.

Jeff Moden (4/2/2014)

---

Koen Verbeeck (4/2/2014)

---

GilaMonster (4/1/2014)

---

In-memory OLTP (hekaton) is for heavy concurrent load (tens of thousands of concurrent connections with thousands of inserts/sec). The advantage is the lock-less, latch-less optimistic...

dup

No, the value...

SQL Guy 1 (4/2/2014)

---

Grant Fritchey (4/2/2014)

---

There's a lot to it. I wrote a book on the topic (look in the links below). But, to get you started, I'd recommend...

It's not the language I have an issue with. It's different, the indenting will take some getting used to, there are odd conventions about how to handle lists and other...

You may want to reopen that case.

PearlJammer1 (4/2/2014)

---

Would the locks that where taken out on the resources by the stored proc that was causing the blocking be held until the log file had been committed to...

So that saturday backup should be clean, since the CheckDB which ran after it was without error.