Ok, I just added those to the group by clause. Look back at the last post, I changed it there.

GilaMonster (4/19/2012)

---

SQLKnowItAll (4/19/2012)

---

To add a bit that people often forget is the uniqueness of the column(s) indexed. If the data is skewed the index may not be very helpful unless...

Thank you!

To add a bit that people often forget is the uniqueness of the column(s) indexed. If the data is skewed the index may not be very helpful unless filtered. ...

GilaMonster (4/19/2012)

---

Sure you...

Eh... Read this by Paul White. http://sqlblog.com/blogs/paul_white/archive/2010/11/01/read-committed-shared-locks-and-rollbacks.aspx

EDIT: My bad response omitted to remove any confusion...

cfradenburg (4/19/2012)

---

This does require a bit of a redesign, but why not keep the warehouse inventory levels in a different table? It probably shouldn't be in the same table...

Ok, so change what I did to UPC instead of product.

Shree-903371 (4/19/2012)

---

I need to use sum on inventory as I was grouping on UPC. To avoid confusion I did not use UPC field.

Now when you run the query below...

Hmm... So you don't want to sum that do you? why not place it as the second column and include that in the grouping.

SELECT

Product,CASE

WHEN Warehouse = 1 THEN Inventory

ELSE 0

END...

I use this:

USE dbName

SELECT Distinct SO.Name

FROM sysobjects SO (NOLOCK)

INNER JOIN syscomments SC (NOLOCK) on SO.Id = SC.ID

AND SO.Type = 'P'

AND SC.Text LIKE '%whatever%'

ORDER BY SO.Name

You can, and it will not require a...

I don't see a problem with a nightly calculation and load into a summary table. 5-10 thousand records a day is nothing. We summarize millions each day, so this...

opc.three (4/19/2012)

---

It is true that BEGIN / END adds clarity, but it does not release us from separating our batches with GO, i.e. this still produces an incorrect result:

use tempdb

go

create...