Link to home
Start Free TrialLog in
Avatar of dvplayltd
dvplayltdFlag for Bulgaria

asked on

Tune SQL – WHERE by 2 fileds in one Table – 2 indexes or 1 index with 2 fields?

Dear experts,

I have the task to tune one SQL 2008R2 DB. I have follow t-SQL

Select Table1.F1,Table1.F2, Table1.F3, Table1.F4,OtherTable.F10,OtherTable.F11 .... ,OtherTable.F12 FROM ….  JOIN ...  WHERE Table1.F1 <getdate() AND Table1.F2=2 and …

My question is focus on Table1 where I search by 2 criteria. I wonder I should create 2 separated indexes on every filed, or one index with 2 fields. I know the best way it to measure this via Execution plan, but I think this is a common situation with common recommended solution. I’m focused on speed; My Table1 will have less than 10 000 records, will be relative rarely write, but will be read from this SP all the time.

And I have the same question, but for other table which will have millions of records and will be heavy read and write as well. Then what is the standard solution?
ASKER CERTIFIED SOLUTION
Avatar of Guy Hengel [angelIII / a3]
Guy Hengel [angelIII / a3]
Flag of Luxembourg image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
in your concrete scenario, there come several possible solution paths:
* clustered index on F2 + F1
* partition on F2 + index on F1
* partition on F1 + index on F2
Avatar of dvplayltd

ASKER

10x, i got what you mean. I'll put first field of the index Date /may have many different values/, then on second position Type which have 4 possible values only.