Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
WHERE IN approach
Message
From
02/03/2017 02:09:55
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
 
 
To
01/03/2017 12:00:27
General information
Forum:
Microsoft SQL Server
Category:
SQL syntax
Environment versions
SQL Server:
SQL Server 2014
OS:
Windows 8.1
Network:
Windows Server 2012
Miscellaneous
Thread ID:
01648591
Message ID:
01648714
Views:
32
>>Probably I don't understand the type of query you are doing. If you have all the values hardcoded then go with that.
>
>Here is an example:
>
>
>SELECT Thread.Numero
> FROM Thread
> WHERE Thread.NoStatus=1 AND (Thread.NoClient=1 OR Thread.NoClient=2)
>
>
>That specific one can benefit of a compound index on NoStatus+NoClient.
>
>
>SELECT Thread.Numero
> FROM Thread
> WHERE Thread.NoStatus=1 AND
>  EXISTS (SELECT ForumCli.Numero FROM ForumCli WHERE ForumCli.NoMember=1 AND (ForumCli.NoClient=1 OR ForumCli.NoClient=2))
>
>
>That specific one uses the EXISTS to see if the child table has records.

I am afraid EXISTS wouldn't help with those hardcoded constants. I meant when there is a relation between the tables. Go with IN or OR approach.
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Previous
Reply
Map
View

Click here to load this message in the networking platform