Briceston (1/15/2014)

---

GilaMonster (1/15/2014)

---

I suspect (without any ability to test) that you want this

WHERE ((([Serial Query].SER_OR_ADM_IND) = 'A'))

AND t1.DISCHARGE_DISP ! = 'VVX'

AND t1.VISIT_DATE = CONVERT(varchar,GETDATE(), 101)

AND (t1.Diag_Code1 =...

I suspect (without any ability to test) that you want this

WHERE ((([Serial Query].SER_OR_ADM_IND) = 'A'))

AND t1.DISCHARGE_DISP ! = 'VVX'

AND t1.VISIT_DATE = CONVERT(varchar,GETDATE(), 101)

AND (t1.Diag_Code1 = '' OR...

What's the purpose here? Why do you want a column dynamically named (I pity the front end app which uses that)

I'm not a fan of dev and prod on the same server (mess up dev and you can take prod down), but don't move just on account of memory, each...

Update or insert a row into a table and check via the front end whether or not you can see the change.

Right, standard edition.

Standard is hard-capped at 2GB of memory. It can't use more so the other 4GB of memory you have on that server is wasted. So the 1.6GB looks...

When you're debugging or performance tuning, try one thing at a time, test, evaluate, try something else. Change a bunch of stuff and you'll never be able to figure out...

Probably means SQL doesn't need more. If you're not running load on it, it won't use more memory than it needs.

That said, that looks like 32-bit without AWE or /3GB....

Books...

Oh, and turn boost priority OFF. It's a setting that should almost never be enabled

Don't use Task Manager to check SQL's memory, it displays incorrect values.

Or, unless you're pressed for space, leave them at 20GB?

rodjkidd (1/15/2014)

---

Oh and I see that @SQLBits has replied saying there will be an announcement soon, just hope it doesn't clash with any of the Saturdays in May / June...

Sort and hash warnings are in-memory operations that don't fit into memory and hence spill to TempDB, they're not an indication that TempDB is too small (that would be autogrow...

It will be, but since it's not referenced anywhere inside the dynamic SQL...