Comments on: SQL SERVER – 2008 – Introduction to Filtered Index – Improve performance with Filtered Index

By: Priya

Priya — Wed, 07 Dec 2011 07:49:16 +0000

HI,

Thanks for the wonderful article with the perfect example.

Keep rocking:)

By: Eric Lall

Eric Lall — Thu, 03 Nov 2011 11:11:17 +0000

Hi Pinal,

Keep up the good work. We all who work in sql server admire your work.

Thanks and best regards,
Eric Lall

By: narendra

narendra — Fri, 23 Sep 2011 09:36:49 +0000

Hi Pinal,

Thanks for the article.

By: Aarti

Aarti — Tue, 03 May 2011 10:26:14 +0000

Hi Pinal,

Thanks for the article.

Nice explanation for SQL Server 2008 new feature

By: Roman Hansen

Roman Hansen — Mon, 11 Apr 2011 19:34:23 +0000

Yes, you can use LIKE in any case.
But…
I don’t understand what you mean with “a non-specified condition.”
As I said before, you can use LIKE and if you still want to cover all the data you always have the normal indexes as you use to use until now without any filter at all.

By: Venkata S Kumar

Venkata S Kumar — Mon, 07 Mar 2011 04:17:34 +0000

hi
iam new to sql server .so i want best examples for coding purpose.plz send me website
Regards
Venkat

By: Sonali

Sonali — Mon, 14 Jun 2010 16:50:12 +0000

Excellent answer with good demonstration of eample.

By: mario

mario — Wed, 28 Apr 2010 15:08:10 +0000

Hi I’m new in the filtered index,I have table with millions of records and I belive that filtered index can help me,I try to use a field (indexed with filtered index) in a inner join but the performance it’s the same

create table invoiceDetail (status int)

create index dbo.FilteredIndex ON invoiceDetail(status) where status in (1,2,4)

–invoiceDetail table has a million of records

So, I have a temporal table with the name filterJoin with one field (filterValue) and two values (1,2)

I do the next query

select *
from invoiceDetail I
inner join filterJoin F On I.status and F.filterValue

the query is too slow

but when i try with

select *
from invoiceDetail I
where status in (1,2)

it’s to fast

I try

create table invoiceDetail (status int)

create index dbo.FilteredIndex ON invoiceDetail(status) where status in (1,2,4)

–invoiceDetail table has a million of records

So, I have a temporal table with the name filterJoin with one field (filterValue) and two values (1,2)

I do the next query

select *
from invoiceDetail I
where I.status in (select * from filterJoin)

it’s too slow and I need filter dinamically

By: vijileads

vijileads — Tue, 10 Nov 2009 06:28:10 +0000

Hi,

good explanation. i am trying to implement…..

By: Furkan Balun

Furkan Balun — Sun, 23 Aug 2009 17:58:44 +0000

Hi,

how many filtered index can we create on a table? we may want to execute a query with a few where condition and what do we have to do in this situation? and the other question is that if we want to execute this query for a non-specified where condition like Title=’Marketing’, do we have to write condition as Title=’%%’ ?? this article is very efficient but i thought theese questions after i read it.good works.thanks

By: Eliezer Figueroa

Eliezer Figueroa — Fri, 17 Jul 2009 15:51:15 +0000

Sometime you cant normalize be cause is a “closed” system but you are required to optimize. This is an administration feature not a developer feature.

By: Anonymous

Anonymous — Wed, 21 Jan 2009 15:18:07 +0000

In this particular instance, if you will be sharing so many titles amongst your employees, you need to normalise your data structure and represent the Title in a separate table, with a FK reference the the Employee table. :)

By: Neil Burnett

Neil Burnett — Wed, 29 Oct 2008 18:41:57 +0000

A major reason I would want to do this on a table or view is to allow the full text service to use filtered indexes based on language. As I work with multilingual databases, I need to create either separate language specific tables for the same data or use views (which is how I currently do it).

It seems filtered views have too many gotchas for me in this situation:-)