You would at least have to remove anything that used a feature available in Enterprise Edition that's not also available in Standard Edition. No compressed tables, etc..

But once...

Hard to determine exactly what you want, but my best guess is something like below; adjust the case conditions to be specifically what you need them to be:

select *

from (

...

mitzyturbo (11/1/2016)

---

As I have 2 log tables to pull data from, how would this work?

do you mean by just having a clustered index by the modified date on both log...

Properly clustering should still allow a merge join, which should be much faster than anything you're having to do now.

Cluster the log table on the relevant arrival datetime that you are comparing by (rather than, presumably, a meaningless identity value). Then query directly from the table, joining to...

drew.allen (10/31/2016)

---

Latin is the base for ALL Romance languages. I have an MA in Linguistics, so I have some idea what...

No, actually COBOL had numeric values as well. For example, packed decimal...

CELKO (10/31/2016)

---

Yep, and nobody takes Latin either. Yet everywhere you...

david.jack (10/31/2016)

---

ScottPletcher (10/28/2016)

---

david.jack (10/28/2016)

---

VAL1 can return NULL unfortunately so using a...

I doubt the vast majority of developers today have even heard of COBOL, and they certainly have never programmed in it.

Yes, it can,...

CELKO (10/28/2016)

---

You do not understand the difference between a string and a numeric in SQL. Registration numbers are called "tag numbers" in data modeling; they are a name of an...

david.jack (10/28/2016)

---

VAL1 can return NULL unfortunately so using a comparison operator...

Seems more confusing than the natural CASE statement to me:

SUM(CASE WHEN VAL1 <> 0 THEN VAL1 ELSE VAL2 END)

You're right. Nvarchar shouldn't be used unless it's needed or realistically could be needed.

For example, if you create a two-character code column, there's no reason to use nvarchar, since...