Solved

Using Like

Posted on 2009-05-13
9
173 Views
Last Modified: 2012-05-06
I'm trying to use "Like" like below but this only looks for exact matches. How can I do this?

Note that F_Alert table has no keys related to the other table.
select * from f_alert where 

   criteria like (select Addressee from LAddress lc

                      inner join customeraddress mca on mca.addressid=lc.id  where mca.customerid = '123')

Open in new window

0
Comment
Question by:Camillia
9 Comments
 
LVL 10

Expert Comment

by:Espavo
ID: 24376717
Try this:
select * from f_alert where 

   criteria like '%(select Addressee from LAddress lc

                      inner join customeraddress mca on mca.addressid=lc.id  where mca.customerid = '123')%'

Open in new window

0
 
LVL 75

Expert Comment

by:Aneesh Retnakaran
ID: 24376720

select *
from f_alert f
where exists
(select null
from LAddress lc
inner join customeraddress mca on mca.addressid=lc.id
where mca.customerid = '123' AND f.criteria like '%'+Addressee+'%')
0
 
LVL 22

Expert Comment

by:8080_Diver
ID: 24377358
Try the following two options.  Using LIKE is bad enough without compounding things with an EXISTS. ;-)

Option 1:
 

SELECT F.* 

FROM f_alert F

INNER JOIN LAddress A

ON F.criteria = A.Addressee

INNER JOIN  customeraddress C

ON C.addressid=A.id  

AND C.customerid LIKE '%' + '123' + '%';
 

Option 2:

SELECT F.* 

FROM f_alert F

INNER JOIN LAddress A

ON F.criteria = A.Addressee

INNER JOIN  customeraddress C

ON C.addressid=A.id  

WHERE C.customerid LIKE '%' + '123' + '%';

Open in new window

0
 
LVL 7

Author Comment

by:Camillia
ID: 24377473
let me see. Thanks. Yeah, like is not good.
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 22

Expert Comment

by:8080_Diver
ID: 24377550
LIKE is Not A Good THing . . . unless it is the only way to get there from here. ;-)
However, when you use LIKE, you just have to be aware that you have just agreed to have potentially very poor performance and, if you are playing with enough data, time outs. ;-)
Where I work, there is an application that may wind up using up to 5 instances of LIKE '%whatever%' on tables with millions of rows . . . and they keep asking me to provide indexes to solve their performance issues. ;-)
0
 
LVL 7

Author Comment

by:Camillia
ID: 24377648
Fraud_alert table has a row with column =330.  LocAddress has a column=33092

It should bring back that "330" row but it doesnt:

select * 

from fraud_alert f 

where exists 

(select null 

from LocAddress lc 

inner join memcustomeraddress mca on mca.addressid=lc.id 

where mca.customerid = '123' AND 

(f.criteria like '%' + PostalCode + '%' OR f.criteria like '%'+Addressee+'%' OR f.criteria like '%'+ Address1 + '%' )
 

)

Open in new window

0
 
LVL 22

Expert Comment

by:8080_Diver
ID: 24378271
You've got your LIKEs cross wired.  (And I still done't like the EXISTS approach but I don't have time to alter that part. ;-)
select * 

from fraud_alert f 

where exists 

(select null 

from LocAddress lc 

inner join memcustomeraddress mca on mca.addressid=lc.id 

where mca.customerid = '123' AND 

(PostalCode like '%' + f.criteria + '%' OR Addressee like '%'+f.criteria+'%' OR Address1 like '%'+ f.criteria + '%' )

 

)

Open in new window

0
 
LVL 22

Accepted Solution

by:
8080_Diver earned 500 total points
ID: 24378322
On second thought, it didn't take too long: ;-)
SELECT f.* 

FROM fraud_alert f 

INNER JOIN 

(

 SELECT PostalCode,

        Addressee,

        Address1 

FROM LocAddress lc 

INNER JOIN memcustomeraddress mca 

   ON mca.addressid=lc.id 

WHERE  mca.customerid = '123'

) Z

ON (Z.PostalCode like '%' + f.criteria + '%' ) OR 

   (Z.Addressee like '%'+f.criteria+'%' ) OR 

   (Address1 like '%'+ f.criteria + '%' );

 

Open in new window

0
 
LVL 7

Author Comment

by:Camillia
ID: 24378484
8080: your last one worked. Let me try one more thing and will post back
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In this article I will describe the Backup & Restore method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
A short film showing how OnPage and Connectwise integration works.
Concerto provides fully managed cloud services and the expertise to provide an easy and reliable route to the cloud. Our best-in-class solutions help you address the toughest IT challenges, find new efficiencies and deliver the best application expe…

932 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now