No. But remember, it's just a guideline. You may need to adjust it up or down for your given situation. But it does give a starting point.

Cars is an extra letter and I'm a completely lazy SOB. I'd rather just have Car, as long as it's clear, right. I mean, not Cr or something else stupid.

The first couple of sentences in the article I linked gives you a calculation. 1gb to the OS for every 4gb of memory up to 16gb. So, if you have...

souLTower (4/12/2014)

---

It's very possible that this happened when the application was converted from Access to SQL7. It was a good find because it caused me to look through the...

I just use SQL Prompt instead of dragging and dropping. It works a lot better and includes all kinds of extra functions.

And yeah, I work for Red Gate, but I...

Also take a look at Louis Davidson and Tim Ford's book on Dynamice Management Views.

SQL Server will consume all the memory you allow it to have. That's how it works. You should allow it as much memory as you can on any give server...

Your best bet for something like this would be to use Extended Events. You can capture execution of queries and it has very good filtering so you can just get...

After you make the change that Gail suggests, here's a very large percentage of everything you need to know about In-Memory OLTP. Make sure you read through all the recommendations...

And don't miss out on free opportunities in your area. SQL Saturday Chicago is happening in just a couple of weeks. SQL Saturday Madison was just a couple of weeks...

Tune the query. Tune the data structure. Tune the indexes. Keep the statistics up to date. That's about all I can based on the query running slow and that's all...

They turned them off to speed up a data load but never turned them back on?

I don't know. Pretty much blazing away at their feet though.

Ah, that makes sense. I was following this question because I was curious if it worked differently than my understanding too. Good to know we both have a handle on...

I'm not sure. It's not something I would try to do. What's the purpose of this approach?

You want to do this live against your database? In short, you're building an additional locking and blocking mechanism on top of SQL Server (assuming I understand what you're suggestion)....