RonKyle (8/1/2013)

---

RonKyle (7/31/2013)

--------------------------------------------------------------------------------

Most would probably say it's overkill, but I prefix my OLTP databases with db, my staging areas with sa, and my OLAP database with dw. The names are...

Same question, why? What...

RonKyle (7/31/2013)

---

Most would probably say it's overkill, but I prefix my OLTP databases with db, my staging areas with sa, and my OLAP database with dw. The names are...

Just remember, query "hints" are not hints, they are commandments. NO_LOCK is not a suggestion that maybe, if the possibility presents itself, where applicable, avoid taking out some locks if...

I would suggest that you also use extended events to capture the execution of the queries. This will show the amount of CPU and I/O each query consumes. That will...

Clarity, clarity, clarity.

You need to make things clear. Keeping the names arbitrarily short does nothing but obscure meaning. You want to know what things are, quick, clear and simple. In...

Erland Sommarskog (7/31/2013)

---

Grant Fritchey (7/31/2013)

---

So much for my stupid Cartesian product statement. You do have that problem. First warning right at the top of the plan indicates you don't have...

christopher_rogala (7/31/2013)

---

Let me start off by saying, I agree that temp tables are much more efficient that variable tables; and try to exclusively use temp tables. That said, you...

So much for my stupid Cartesian product statement. You do have that problem. First warning right at the top of the plan indicates you don't have JOIN criteria. Apologies Kevin.

I'd...

With that, I suppose it would then be possible to successfully break things down. It still depends on accurate entry, but having a mechanism to validate the entry changes things...

My suggestion... don't do that. Unless you're building some sort of address reporting engine that counts the number of references to street vs. road in official address usages, you will...

You can pretty quickly set up extended events to capture the query and it's performance and then recapture it after adding the index. You can also capture the execution plans...

It doesn't look like you have cartesian joins. You have defined join criteria. A cartesian is when you don't have join criteria defined and every row is joined on every...

You'll have to work with the vendor to either supply you with the information of how your system is configured, or get them to give you read privileges to the...

That will show you what is currently in the cache. It is an aggregation of executions for each of your statements in cache, the number of times called, average CPU,...