Advertisement

03.13.2008 at 10:22PM PDT, ID: 23240913
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
9.6

Finding related records in a table and including the reason in the resultset

Asked by craigsweet in SQL Server 2005, MS SQL Server

Tags: ,

I have one table, called Orders, that contains all of the data i want to query.  Every time a user looks at an order (in a given part of the application) i would like to tell him if there are related fraudulent orders.  For the purposes of our discussion, a fraudulent order has the KnownFraud flag set to 1.  These are previous orders that were marked as fraud for one reason or another.  

I created a stored procedure, which is attached, that will return the resultset.  I pass in the three primary key fields, and it simply looks for fraudulent records that are related.  By related i'm just saying for now that a few fields are equal.  

So, to clear this up, if i have an order with credit card = '123' and another knownfraud order exists with that same credit card number, or buyer's address, etc. then it'll be returned by this query. This query works as is

Here is my question:  I would like to also return a string indicating why this record is related.  So, for the credit card example i would say "matching credit card", for buyer's address i'd say "matching Buyer Addr." or something like that.  Is there a way to modify this query to accomplish this?  
Start Free Trial 
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:

CREATE PROCEDURE [dbo].[getRelatedFraud] (
	@OrderID	NVarChar( 50 ),
	@Store		NVarChar( 10 ),
	@OrderDate	SmallDateTime)
AS
BEGIN
 
	DECLARE @CCNum	  NVarChar ( 100 )
	DECLARE @BuyLName	  NVarChar ( 50 )
	DECLARE @RcvLName   NVarChar ( 50 )
	DECLARE @RcvStreet  NVarChar ( 255 )
	DECLARE @BuyStreet  NVarChar ( 255 )
 
	select	@CCNum = CreditCardNumber, 
			@BuyLName=BuyLName,
			@RcvLName=RcvLName,
			@BuyStreet=BuyStreet,
			@RcvStreet=RcvStreet
		FROM Orders 
		WHERE OrderID=@OrderID AND Store=@Store
 
	select OrderID, Store, OrderDate as 'Order Date', cardtype as 'Card Type', BuyLName
		FROM Orders
		Where KnownFraud=1 and Orderid<>@OrderID and 
			(CreditCardNumber=@CCNum or 
			 upper(buylname)=upper(@buylname) or 
			 upper(rcvlname)=upper(@rcvlname) or 
			 upper(buystreet)=upper(@buystreet) or 
			 upper(rcvstreet)=upper(@rcvstreet))
 
END
[+][-]03.13.2008 at 11:41PM PDT, ID: 21123428

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]03.13.2008 at 11:50PM PDT, ID: 21123445

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: SQL Server 2005, MS SQL Server
Tags: t-sql, 2005
Sign Up Now!
Solution Provided By: maradam
Participating Experts: 2
Solution Grade: A
 
 
 
Loading Advertisement...
20081112-EE-VQP-42 / EE_QW_2_20070628