Exclude Duplicates based on column value

I have a view SSG_CATALOG that exports data for our catalog with columns  ITEMNMBR, ITEMDESC, DEALERPRICE, PRCLEVEL my problem is that because we used different price levels foreach item it creates a row for each item. For example Item ACCP2015BR1 has a price level of A, AAA, and B but the DEALERPRICE is the same for all 3 levels so I just want to return only the A price level if the DEALERPRICE for AAA and B = A.

Price Levels
skull52IT director Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David ToddSenior Database AdministratorCommented:
Hi,

My thought is a group by with the min of prclevel

ie
select
    c.itemnmbr
    , c.itemdesc
    , c.dealerprice
    , min( c.prclevel ) as PRCLEVEL
from dbo.SSG_CATALOG c
where
    somewhereclause
group by
    c.itemnmbr
    , c.itemdesc
    , c.dealerprice
order by
    c.itemnmbr
    , c.itemdesc
    , c.dealerprice
;

HTH
  David
0
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
One way would be to use RANK() to order the PRICELEVEL values, grouped by ITEMNBR and DEALERPRICE, alphabetically (Assuming A is better than AAA is better than B), then just grab all the rows that sort first.  
SELECT a.ITEMNMBR, a.ITEMDESC, a.DEALERPRICE, a.PRICELEVEL
FROM (
   SELECT ITEMNBR, ITEMDESC, DEALERPRICE, PRICELEVEL, 
      RANK() OVER (PARTITION BY ITEMNMBR, DEALERPRICE ORDER BY PRICELEVEL) as rank_order) a
WHERE a.rank_order = 1

Open in new window

0
David ToddSenior Database AdministratorCommented:
Hi,

I'd be interested in the execution plan costs - if there are major differences between these two approaches.

Regards
  David
0
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

skull52IT director Author Commented:
Thanks for the responses

David,
 I get the following error from your suggestion
Msg 4145, Level 15, State 1, Line 9
An expression of non-boolean type specified in a context where a condition is expected, near 'group'.

Jim,
I cant even get yours to run I think the reference to the  SSG_CATALOG is missing
0
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
<correction to my above code.  You may have to check the column names, as the image was hard to read>
SELECT a.ITEMNMBR, a.ITEMDESC, a.DEALERPRICE, a.PRICELEVEL
FROM (
   SELECT ITEMNBR, ITEMDESC, DEALERPRICE, PRICELEVEL, 
      RANK() OVER (PARTITION BY ITEMNMBR, DEALERPRICE ORDER BY PRICELEVEL) as rank_order
   FROM SSG_CATALOG) a
WHERE a.rank_order = 1

Open in new window

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David ToddSenior Database AdministratorCommented:
Hi,

Did you just cut and paste my answer, or did you read it? You'll need to edit the where clause (or delete it!)

Regards
  David
0
skull52IT director Author Commented:
David, My bad I did miss the WHERE clause.

Jim, thanks for fixing that, I knew the Reference to the table was missing so I added it

OK, so with using Jim's solution I get 25071 rows With David's I get 24974 a difference of 97 rows
0
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
>OK, so with using Jim's solution I get 25071 rows With David's I get 24974 a difference of 97 rows
Since we don't have access to your data set, you will have to identify the 97 row difference and troubleshoot.   Perhaps there are duplicate rows being returned, in which case you can replace SELECT with SELECT DISTINCT.
0
skull52IT director Author Commented:
Jim,
I used DISTINCT but it only returned 1 row less, and I examined the results and they look good so I am going with your solution. Thanks to David for his solution also.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.