﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Article Discussions / Article Discussions by Author / Discuss content posted by Carleton  / Wild Join Question / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 22 May 2013 13:34:46 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Wild Join Question</title><link>http://www.sqlservercentral.com/Forums/Topic838852-2566-1.aspx</link><description>[quote][b]Chris Carter-210078 (12/30/2009)[/b][hr]The complete answer should be “It depends”.  If you have a case sensitive collation designator you will get:Msg 208, Level 16, State 0, Line 3Invalid object name '#table1'.Since the script created a table #Table1 and tries to reference #table1[/quote] You're correct but based on what's given then you'll need to set collation to something that will provide with results for this scenario.</description><pubDate>Wed, 06 Jan 2010 03:21:31 GMT</pubDate><dc:creator>BudaCli</dc:creator></item><item><title>RE: Wild Join Question</title><link>http://www.sqlservercentral.com/Forums/Topic838852-2566-1.aspx</link><description>The complete answer should be “It depends”.  If you have a case sensitive collation designator you will get:Msg 208, Level 16, State 0, Line 3Invalid object name '#table1'.Since the script created a table #Table1 and tries to reference #table1</description><pubDate>Wed, 30 Dec 2009 08:06:51 GMT</pubDate><dc:creator>Chris Carter-210078</dc:creator></item><item><title>RE: Wild Join Question</title><link>http://www.sqlservercentral.com/Forums/Topic838852-2566-1.aspx</link><description>[quote][b]Hugo Kornelis (12/24/2009)[/b][hr][quote][b]Carleton (12/23/2009)[/b][hr]If you are unsure if the field contains a wildcard character when joining using the LIKE operator, you can avoid false positive results by observing this tip:[/quote]But what is the point of using LIKE if you do this? Why not simply use the = operator?[/quote]In general, you probably wouldn't use LIKE exactly like that, but with your own wildcards attached. For example, you may want to see if a string contains another string in its entirety. If the second string might have a wildcard in it, you'd have to do something like:[code="sql"]select * from #table1 t1 inner join #table2 t2 on t1.Col1 like '%' + REPLACE(REPLACE(t2.Col1,'%','[%]'),'_','[_]') + '%'[/code]Otherwise, the wildcard in the second string may cause false positives.</description><pubDate>Thu, 24 Dec 2009 05:57:48 GMT</pubDate><dc:creator>sknox</dc:creator></item><item><title>RE: Wild Join Question</title><link>http://www.sqlservercentral.com/Forums/Topic838852-2566-1.aspx</link><description>[quote][b]Carleton (12/23/2009)[/b][hr]If you are unsure if the field contains a wildcard character when joining using the LIKE operator, you can avoid false positive results by observing this tip:[/quote]But what is the point of using LIKE if you do this? Why not simply use the = operator?</description><pubDate>Thu, 24 Dec 2009 05:10:27 GMT</pubDate><dc:creator>Hugo Kornelis</dc:creator></item><item><title>Wild Join Question</title><link>http://www.sqlservercentral.com/Forums/Topic838852-2566-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/questions/Wild+Card/68252/"&gt;Wild Join Question&lt;/A&gt;[/B]</description><pubDate>Wed, 23 Dec 2009 22:14:47 GMT</pubDate><dc:creator>Carleton</dc:creator></item></channel></rss>